CVE-2026-2297

MEDIUMNVD 5.75.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% 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, nvd
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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
Severity57% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

Published

March 4, 2026

Last Modified

August 13, 2026

Advisory Details (8)

Auto-updated May 1, 2026
Patch available.
generic

oss-security - Fwd: [CVE-2026-2297] SourcelessFileLoader does not use io.open_code()

http://www.openwall.com/lists/oss-security/2026/03/05/6
generic

gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoader uses io.open_code by zooba · Pull Request #145507 · python/cpython · GitHub

https://github.com/python/cpython/pull/145507
generic

[CVE-2026-2297] SourcelessFileLoader does not use io.open_code() · Issue #145506 · python/cpython · GitHub

https://github.com/python/cpython/issues/145506
generic

[3.14] gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoade… · python/cpython@e58e980 · GitHub

https://github.com/python/cpython/commit/e58e9802b9bec5cdbf48fc9bf1da5f4fda482e86
generic

gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoader uses … · python/cpython@a51b1b5 · GitHub

https://github.com/python/cpython/commit/a51b1b512de1d56b3714b65628a2eae2b07e535e
generic

[3.10] gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoade… · python/cpython@876858c · GitHub

https://github.com/python/cpython/commit/876858c9f65d9ab656c7fa639f268ce7856d89dd
generic

[3.11] gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoade… · python/cpython@69ddd9b · GitHub

https://github.com/python/cpython/commit/69ddd9bb2cc4bd69b1565647c18659c6a789ccd9
generic

[3.13] gh-145506: Fixes CVE-2026-2297 by ensuring SourcelessFileLoade… · python/cpython@482d6f8 · GitHub

https://github.com/python/cpython/commit/482d6f8bdba9da3725d272e8bb4a2d25fb6a603e

Vendor Advisories for CVE-2026-2297(13)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3.10-venv (3.10.12-1~22.04.16) @ jammy2026-08-05ubuntu
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatpython3.12-0:3.12.13-2.el10_22026-05-19redhat
redhatpython3.14-0:3.14.4-2.el10_22026-05-19redhat
redhatpython3.14-0:3.14.4-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el9_82026-05-19redhat
redhatpython3.12-0:3.12.13-2.el8_102026-04-27redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-14-main-3.14.4-1.hum12026-04-11redhat
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

(13 across 8 ecosystems)
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 7.3.21+dfsg-4 (9 versions)
  • every version up to 7.3.22+dfsg-1: fixed in 7.3.22+dfsg-1
—
python3.133.13.11-1 ... 3.13.9-1 (7 versions)
  • every version up to 3.13.14-1: fixed in 3.13.14-1
—
python3.143.14.0-1 ... 3.14.3-3 (17 versions)
  • every version up to 3.14.3-4: fixed in 3.14.3-4
—
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)
  • every version on: no fix on record
—
python3.93.9.2-1 ... 3.9.2-1+deb11u6 (7 versions)
  • every version up to 3.9.2-1+deb11u7: fixed in 3.9.2-1+deb11u7
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.11+dfsg-2 ... 8.0.0+dfsg-1 (31 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.2-6+deb12u7 (8 versions)
  • every version up to 3.11.2-6+deb12u8: fixed in 3.11.2-6+deb12u8
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version on: no fix on record
—
python3.133.13.5-2
  • every version up to 3.13.5-2+deb13u1: fixed in 3.13.5-2+deb13u1
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.14-r0: fixed in 3.12.14-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.5-r0: fixed in 3.14.5-r0
—

Weakness Classification(1)

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 7× in last 7d / 24× 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 225 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-2297?
CVE-2026-2297 is a medium vulnerability published on March 4, 2026. The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.
When was CVE-2026-2297 disclosed?
CVE-2026-2297 was first published on March 4, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2297 actively exploited?
CVE-2026-2297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2297?
CVE-2026-2297 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-2297?
A fix for CVE-2026-2297 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2297 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-2297

Explore →

Is Your Infrastructure Affected by CVE-2026-2297?

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

Book a Demo →Browse All CVEs