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 GET RESPONSE. 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-49010
This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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).
- 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
- 6.8(medium)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Aug 3, 2026CVE 2025 49010 · OpenSC/OpenSC Wiki · GitHub
https://github.com/OpenSC/OpenSC/wiki/CVE-2025-49010Stack-buffer-overflow WRITE in GET RESPONSE · Advisory · OpenSC/OpenSC · GitHub
https://github.com/OpenSC/OpenSC/security/advisories/GHSA-q5cf-5wmx-9wh4Vendor Advisories for CVE-2025-49010(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opensc | 0.21.0-1 ... 0.27.1-2 (23 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opensc | 0.23.0-0.3 ... 0.27.1-2 (18 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opensc | 0.26.1-2 ... 0.27.1-2 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| opensc | 0.26.1-2, 0.26.1-3 | 0.27.0~rc1-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 31× 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-09-15 03:09 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 21:59 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:46 UTCEPSS rescore
- 2026-09-05 15:28 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-02 12:44 UTCOSV refresh
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:38 UTCEPSS rescore
- 2026-08-30 19:16 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-24 09:22 UTCEPSS rescore
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-20 22:54 UTCEPSS rescore
Show 43 moreShow fewer
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:47 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 09:46 UTCEG score recompute
- 2026-08-16 09:46 UTCVendor advisory
- 2026-08-16 02:13 UTCEPSS rescore
- 2026-08-15 01:29 UTCEPSS rescore
- 2026-08-14 06:09 UTCEG score recompute
- 2026-08-14 06:09 UTCVendor advisory
- 2026-08-13 21:59 UTCEPSS rescore
- 2026-08-12 20:29 UTCEG score recompute
- 2026-08-12 20:29 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:41 UTCEPSS rescore
- 2026-08-11 09:08 UTCEG score recompute
- 2026-08-11 09:08 UTCVendor advisory
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 07:25 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:43 UTCEG score recompute
- 2026-08-09 05:43 UTCVendor advisory
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-07 15:54 UTCEG score recompute
- 2026-08-07 15:54 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:40 UTCEG score recompute
- 2026-08-06 00:40 UTCVendor advisory
- 2026-08-05 19:16 UTCEPSS rescore
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-03 23:00 UTCEG score recompute
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 15:03 UTCEG score recompute▲ 3.00
- 2026-08-02 15:03 UTCVendor advisory
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 12:52 UTCEG score recompute
- 2026-07-27 12:52 UTCVendor advisory
Frequently asked(5)
What is CVE-2025-49010?
When was CVE-2025-49010 disclosed?
Is CVE-2025-49010 actively exploited?
What is the CVSS score of CVE-2025-49010?
How do I remediate CVE-2025-49010?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49010
Is Your Infrastructure Affected by CVE-2025-49010?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.