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%CVSS: 5.7Exploit: None knownExposed: 0

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.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity57% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

March 4, 2026

Last Modified

August 13, 2026

Advisory Details (8)

Auto-updated May 1, 2026
No patch confirmed yet.
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 / EcosystemFixed in / 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

(10 across 5 ecosystems)
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.21+dfsg-4 (9 versions)7.3.22+dfsg-1—
python3.133.13.11-1 ... 3.13.9-1 (7 versions)3.13.14-1—
python3.143.14.0-1 ... 3.14.3-3 (17 versions)3.14.3-4—
Debian:11(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python3.93.9.2-1 ... 3.9.2-1+deb11u6 (7 versions)3.9.2-1+deb11u7—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.2-6+deb12u7 (8 versions)3.11.2-6+deb12u8—
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-23.13.5-2+deb13u1—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—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 / 62× 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 185 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 88.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2297, 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-2297

Explore →

Is Your Infrastructure Affected by CVE-2026-2297?

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

Start Free Scan →Browse All CVEs