OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, feeding a crafted input to the fuzz_pkcs15_reader harness causes OpenSC to perform an out-of-bounds heap read in the X.509/SPKI handling path. Specifically, sc_pkcs15_pubkey_from_spki_fields() allocates a zero-length buffer and then reads one byte past the end of that allocation. This issue has been patched in version 0.27.0.
CVE-2025-66037
This low-severity CVE scores 3.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 3.9(low)
- EG Risk
- 18(Track)EG Risk 18/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 computedSeverity39% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
References (2)
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/security/advisories/GHSA-m58q-rmjm-mmfx
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/wiki/CVE-2025-66037
Vendor Advisories for CVE-2025-66037(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 14:12 UTCEPSS rescore
- 2026-07-27 12:52 UTCEG score recompute
- 2026-07-27 12:52 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
Frequently asked(5)
What is CVE-2025-66037?
When was CVE-2025-66037 disclosed?
Is CVE-2025-66037 actively exploited?
What is the CVSS score of CVE-2025-66037?
How do I remediate CVE-2025-66037?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-66037
Is Your Infrastructure Affected by CVE-2025-66037?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.