OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, an attacker with physical access to the computer at the time user or administrator uses a token can cause a stack-buffer-overflow WRITE in card-oberthur. The attack requires crafted USB device or smart card that would present the system with specially crafted responses to the APDUs. This issue has been patched in version 0.27.0.
CVE-2025-66215
This low-severity CVE scores 3.8 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.8(low)
- EG Risk
- 17(Track)EG Risk 17/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 computedSeverity38% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/commit/efd1d479832141bcf705c2f47655ada4d5f92f5d
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/pull/3436
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/security/advisories/GHSA-q5fc-cw56-hwp2
- security-advisories@githubhttps://github.com/OpenSC/OpenSC/wiki/CVE-2025-66215
Vendor Advisories for CVE-2025-66215(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 5× in last 7d / 5× 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-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
Frequently asked(5)
What is CVE-2025-66215?
When was CVE-2025-66215 disclosed?
Is CVE-2025-66215 actively exploited?
What is the CVSS score of CVE-2025-66215?
How do I remediate CVE-2025-66215?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-66215
Is Your Infrastructure Affected by CVE-2025-66215?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.