How severe is CVE-2026-2297?

CVE-2026-2297 has a CVSS 4.0 base score of 5.7, rated medium severity.

Is CVE-2026-2297 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-2297?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-2297 have an EU (EUVD) identifier?

Yes. CVE-2026-2297 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9498.

When was CVE-2026-2297 published?

CVE-2026-2297 was published on 2026-03-04 and last updated on 2026-06-17.

CVE-2026-2297

CVE-2026-2297 is a medium-severity vulnerability with a CVSS 4.0 base score of 5.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-668.

Key facts

Severity: Medium (CVSS 4.0 base score 5.7)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-9498
Weakness: CWE-668
Published: 2026-03-04
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-2297?: 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.
How severe is CVE-2026-2297?: CVE-2026-2297 has a CVSS 4.0 base score of 5.7, rated medium severity.
Is CVE-2026-2297 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-2297?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-2297 have an EU (EUVD) identifier?: Yes. CVE-2026-2297 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-9498.
When was CVE-2026-2297 published?: CVE-2026-2297 was published on 2026-03-04 and last updated on 2026-06-17.

References

Other CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities

CVE-2025-2857 — Critical (CVSS 10.0): Following the recent Chrome sandbox escape (CVE-2025-2783), various Firefox developers identified a similar pattern in…
CVE-2019-8779 — Critical (CVSS 10.0): A logic issue applied the incorrect restrictions. This issue was addressed by updating the logic to apply the correct…
CVE-2012-1846 — Critical (CVSS 10.0): Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging…
CVE-2022-43684 — Critical (CVSS 9.9): ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow…
CVE-2022-24900 — Critical (CVSS 9.9): Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer.…
CVE-2019-16541 — Critical (CVSS 9.9): Jenkins JIRA Plugin 3.0.10 and earlier does not declare the correct (folder) scope for per-folder Jira site…

Browse all CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities →