CVE-2025-66215: OpenSC: Stack-buffer-overflow WRITE in card-oberthur
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: OpenSC OpenSC 0.27.0; azl3 opensc 0.26.1-1 on Azure Linux 3.0 0.27.1-1; cbl2 opensc 0.23.0-5 on CBL Mariner 2.0 0.23.0-6.
- Severity is disputed: the assigning authority (CNA) scores it 3.8, NVD 6.8.
Low priority for now. Upgrade to OpenSC OpenSC 0.27.0; azl3 opensc 0.26.1-1 on Azure Linux 3.0 0.27.1-1; cbl2 opensc 0.23.0-5 on CBL Mariner 2.0 0.23.0-6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 30, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-121
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.8
- CNA · GitHub_M
- 3.8
- 3.0 point gap
CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| opensc project | opensc | cpe:2.3:a:opensc_project:opensc |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
OpenSC OpenSC
- < 0.27.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensc project openscbefore 0.27.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | opensc | from 0 | — |
| Debian:14 | opensc | before 0.27.0~rc1-1 | 0.27.0~rc1-1 |
| openSUSE:Leap 16.0 | opensc | before 0.26.1-160000.3.1 | 0.26.1-160000.3.1 |
| openSUSE:Tumbleweed | opensc | before 0.27.1-1.1 | 0.27.1-1.1 |
| SUSE:Linux Enterprise Micro 5.2 | opensc | before 0.19.0-150100.3.34.1 | 0.19.0-150100.3.34.1 |
| SUSE:Linux Enterprise Micro 5.3 | opensc | before 0.22.0-150400.3.17.1 | 0.22.0-150400.3.17.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | opensc | before 0.22.0-150600.11.11.1 | 0.22.0-150600.11.11.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | opensc | before 0.13.0-3.36.1 | 0.13.0-3.36.1 |
| SUSE:Linux Micro 6.2 | opensc | before 0.26.1-160000.3.1 | 0.26.1-160000.3.1 |
Same product
opensc project: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-6502sc_context_create in ctx.c in libopensc in OpenSC 0.19.0 has a memory leak, as demonstrated by a call from eidenv.31Monitor
- CVE-2021-34193Stack overflow vulnerability in OpenSC smart card middleware before 0.23 via crafted responses to APDUs.30Monitor
- CVE-2019-16058An issue was discovered in the pam_p11 component 0.2.0 and 0.3.0 for OpenSC.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-66037Mar 30, 2026 · OpenSC: Out of Bounds vulnerability27Monitor
- ← EarlierCVE-2025-66038Mar 30, 2026 · OpenSC: `sc_compacttlv_find_tag` can return out-of-bounds pointers27Monitor
- Later →CVE-2026-40510May 29, 2026 · OpenSC < 0.27.0-rc1 Stack Buffer Overflow via piv_process_history() in card-piv.c4Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| OpenSC OpenSC | 0.27.0 · description | Vendor (CNA) |
| azl3 opensc 0.26.1-1 on Azure Linux 3.0 | 0.27.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 opensc 0.23.0-5 on CBL Mariner 2.0 | 0.23.0-6 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:opensc | 0.27.0~rc1-1 · Debian:14 | Package registry (OSV) |
| opensuse:opensc | 0.27.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:opensc | 0.19.0-150100.3.34.1 · SUSE:Linux Enterprise Micro 5.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-490100 days apartOpenSC: Stack-buffer-overflow WRITE in GET RESPONSE27Monitor
- CVE-2026-4051060 days apartOpenSC < 0.27.0-rc1 Stack Buffer Overflow via piv_process_history() in card-piv.c4Monitor
- CVE-2026-4052860 days apartOpenSC < 0.27.0 Buffer Overrun in do_key_value() via profile.c4Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.