CVE-2026-5713

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 14, 2026

Last Modified

July 31, 2026

Advisory Details (5)

Auto-updated Jul 31, 2026
Patch available. 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
Web page

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/
Web page

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

https://github.com/python/cpython/issues/148178
GitHub pull request

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

Vendor Advisories for CVE-2026-5713(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
python3.143.14.0-1 ... 3.14.5~rc1-1 (22 versions)
  • every version up to 3.14.5-1: fixed in 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 11× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5713?
CVE-2026-5713 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-5713 published?
The CVE record for CVE-2026-5713 was published on April 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 31, 2026; the record at its source may have been updated since.
Is CVE-2026-5713 actively exploited?
CVE-2026-5713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5713?
CVE-2026-5713 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-5713?
A fix for CVE-2026-5713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5713 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs