dbcve.org
OpenscApplication · Opensc Project

CVE-2025-49010

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-30
Fix available
A fix is available. Upgrade to 0.27.0 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenSC before version 0.27.0 contains a stack-buffer-overflow write vulnerability in the GET RESPONSE handler. An attacker with physical access to a system at the time a user or administrator uses a smart card token can exploit this by presenting a crafted USB device or smart card that sends specially manipulated APDU responses.

MitigationUpgrade OpenSC to version 0.27.0 or later to patch the vulnerability. Additionally, restrict physical access to systems during smart card token operations and monitor for unusual USB devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenscApplication
Affected:< 0.27.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed OpenSC version
    Run 'opensc-tool --version' on Linux, check Windows program files, or query package manager: 'dpkg -l | grep opensc' (Debian) or 'rpm -q opensc' (RHEL)
    Affected if Version returned is less than 0.27.0 or no version is returned but OpenSC is installed
  2. Check OpenSC library file version
    Locate the opensc library (libopensc.so on Linux, opensc-pkcs11.dll on Windows) and query its file version property
    Affected if File version is below 0.27.0
  3. Verify if OpenSC is loaded or configured for smart card use
    Check for OpenSC middleware in system smart card configuration: review /etc/opensc.conf on Linux or Windows registry under HKLM\SOFTWARE\OpenSC Project\OpenSC
    Affected if OpenSC configuration exists and the service is active or available for smart card operations
  4. Confirm smart card reader or token activity on the system
    Review system logs for smart card reader detection or PKCS#11 token usage events
    Affected if Smart card operations have been performed using OpenSC on this system

System is affected if OpenSC version is below 0.27.0 and the system is used for smart card token operations where physical access could be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.27.0 or later
Fixed in 0.27.0
Interim mitigation

Upgrade OpenSC to version 0.27.0 or later to patch the vulnerability. Additionally, restrict physical access to systems during smart card token operations and monitor for unusual USB devices.

Recommended fix High confidence

0.27.0

  1. 1. Check the currently installed OpenSC version using 'opensc-tool --version' or your system's package manager
  2. 2. Upgrade OpenSC to version 0.27.0 or later
  3. 3. For package manager installations: run 'apt-get update && apt-get install opensc' (Debian/Ubuntu) or 'yum update opensc' (RHEL/CentOS) or the equivalent for your distribution
  4. 4. For source builds: download OpenSC 0.27.0 from the official GitHub releases and rebuild
  5. 5. Verify the installed version is 0.27.0 or later using 'opensc-tool --version'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opensc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data