CVE-2026-5713

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

The "profiling.sampling" module (Python 3.15+) and "asyncio introspection capabilities" (3.14+, "python -m asyncio ps" and "python -m asyncio pstree") features could be used to read and write addresses in a privileged process if that process connected to a malicious or "infected" Python process via the remote debugging feature. This vulnerability requires persistently and repeatedly connecting to the process to be exploited, even after the connecting process crashes with high likelihood due to ASLR.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 14, 2026

Last Modified

July 31, 2026

Advisory Details (5)

Auto-updated Jul 31, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
github_commit

commit 316f6265b7f9 (python/cpython)

Fix landed in python/cpython commit 316f6265b7f9 — awaiting tagged release

https://github.com/python/cpython/commit/316f6265b7f9ca4ffed5346b747475ef1943f35d
github_commit

commit 289fd2c97a7e (python/cpython)

Fix landed in python/cpython commit 289fd2c97a7e — awaiting tagged release

https://github.com/python/cpython/commit/289fd2c97a7e5aecb8b69f94f5e838ccfeee7e67
generic

Mailman 3 [CVE-2026-5713] Out-of-bounds read/write during remote debugging when connecting to malicious target - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/OG4RHARYSNIE22GGOMVMCRH76L5HKPLM/
generic

Harden validation of remote debugging offset tables · Issue #148178 · python/cpython · GitHub

https://github.com/python/cpython/issues/148178
github_pr

gh-148178: Validate remote debug offset tables on load

Fix merged in python/cpython PR #148187 on 2026-04-13 — awaiting tagged release

https://github.com/python/cpython/pull/148187

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython3.14-0:3.14.4-2.el9_82026-05-19redhat
redhatpython3.14-0:3.14.4-2.el10_22026-05-19redhat
redhatpython3-14-main-3.14.4-2.hum12026-04-21redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-13-main-3.13.13-1.hum12026-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python3.143.14.0-1 ... 3.14.5~rc1-1 (22 versions)3.14.5-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 176 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 06:49 UTCEG score recompute
  14. 2026-08-16 06:49 UTCVendor advisory
  15. 2026-08-16 06:49 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 04:52 UTCEG score recompute
  18. 2026-08-14 04:52 UTCVendor advisory
  19. 2026-08-14 04:52 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 19:06 UTCEG score recompute
  22. 2026-08-12 19:06 UTCVendor advisory
  23. 2026-08-12 19:06 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 03:19 UTCEG score recompute
Show 75 more
  1. 2026-08-11 03:19 UTCVendor advisory
  2. 2026-08-11 03:18 UTCGHSA enrichment
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-10 03:46 UTCEG score recompute
  5. 2026-08-10 03:46 UTCVendor advisory
  6. 2026-08-10 03:46 UTCGHSA enrichment
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-09 04:13 UTCEG score recompute
  9. 2026-08-09 04:13 UTCVendor advisory
  10. 2026-08-09 04:13 UTCGHSA enrichment
  11. 2026-08-08 16:37 UTCEPSS rescore
  12. 2026-08-07 13:49 UTCEG score recompute
  13. 2026-08-07 13:49 UTCVendor advisory
  14. 2026-08-07 13:49 UTCGHSA enrichment
  15. 2026-08-06 13:47 UTCEPSS rescore
  16. 2026-08-05 23:30 UTCEG score recompute
  17. 2026-08-05 23:30 UTCVendor advisory
  18. 2026-08-05 23:30 UTCGHSA enrichment
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-04 10:39 UTCEPSS rescore
  21. 2026-08-03 21:44 UTCEG score recompute
  22. 2026-08-03 21:44 UTCVendor advisory
  23. 2026-08-03 21:44 UTCGHSA enrichment
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 13:27 UTCEG score recompute
  26. 2026-08-02 13:27 UTCVendor advisory
  27. 2026-08-02 13:27 UTCGHSA enrichment
  28. 2026-08-02 02:27 UTCEPSS rescore
  29. 2026-08-01 04:16 UTCEPSS rescore
  30. 2026-07-31 14:25 UTCEG score recompute
  31. 2026-07-31 14:25 UTCVendor advisory
  32. 2026-07-31 14:25 UTCGHSA enrichment
  33. 2026-07-31 14:09 UTCEG score recompute
  34. 2026-07-31 14:09 UTCVendor advisory
  35. 2026-07-31 14:09 UTCGHSA enrichment
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-27 14:14 UTCEPSS rescore
  40. 2026-07-25 14:18 UTCEPSS rescore
  41. 2026-07-25 14:18 UTCEPSS rescore
  42. 2026-07-24 14:18 UTCEPSS rescore
  43. 2026-07-24 14:18 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:20 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-22 14:08 UTCEPSS rescore
  49. 2026-07-21 15:25 UTCEPSS rescore
  50. 2026-07-21 15:25 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-20 11:02 UTCOSV refresh
  53. 2026-07-19 14:31 UTCEPSS rescore
  54. 2026-07-19 02:29 UTCEPSS rescore
  55. 2026-07-18 10:04 UTCEPSS rescore
  56. 2026-07-16 17:03 UTCEPSS rescore
  57. 2026-07-15 16:57 UTCEPSS rescore
  58. 2026-07-15 02:00 UTCEPSS rescore
  59. 2026-07-15 02:00 UTCEPSS rescore
  60. 2026-07-13 22:31 UTCEPSS rescore
  61. 2026-07-13 06:13 UTCEPSS rescore
  62. 2026-07-13 06:13 UTCEPSS rescore
  63. 2026-07-12 05:46 UTCEPSS rescore
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-09 19:10 UTCEPSS rescore
  68. 2026-07-08 15:16 UTCEPSS rescore
  69. 2026-07-08 15:16 UTCEPSS rescore
  70. 2026-07-07 13:46 UTCEPSS rescore
  71. 2026-07-07 13:46 UTCEPSS rescore
  72. 2026-07-06 02:23 UTCEPSS rescore
  73. 2026-07-06 02:23 UTCEPSS rescore
  74. 2026-07-04 06:31 UTCEPSS rescore
  75. 2026-07-04 06:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5713?
CVE-2026-5713 is a medium vulnerability published on April 14, 2026. The "profiling.sampling" module (Python 3.15+) and "asyncio introspection capabilities" (3.14+, "python -m asyncio ps" and "python -m asyncio pstree") features could be used to read and write addresses in a privileged process if that process connected to a malicious or "infected" Python process via…
When was CVE-2026-5713 disclosed?
CVE-2026-5713 was first published in the National Vulnerability Database on April 14, 2026, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5713 actively exploited?
CVE-2026-5713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-5713?
CVE-2026-5713 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-5713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5713, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5713

Explore →

Is Your Infrastructure Affected by CVE-2026-5713?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.