VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

opensc: vulnerability history, versions and safety

opensc is a package in the Debian ecosystem. Vulert records 97 vulnerabilities for it across 22 releases, from Nov -0001 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
97 vulnerabilities recorded U97
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 01 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all opensc vulnerabilities

Vulert verdict on opensc i

Updated on 23 Oct 2026

Careful: 6 of the 97 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 97 vulnerabilities on record across 2026 years, 2 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 97 over 2026 years · 2 in the last year i
  • Latest disclosure 01 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 6 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for opensc, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 22 of 22 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 4
  • 2008 4
  • 2009 4
  • 2011 2
  • 2018 26
  • 2019 10
  • 2020 8
  • 2022 10
  • 2023 8
  • 2024 19
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 97 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for opensc

The 5 most severe of 97 vulnerabilities recorded for this package

Search all 97 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Incorrect RSA Key Generation in OpenSC 7.5 high 0.11.8 11 May 2009
Stack Overflow Vulnerability in OpenSC Package: Critical Risk in Smart Card Middleware 7.5 high 0.21.0-1+deb11u1 22 Aug 2023
Memory Leak in libopensc in OpenSC 0.19.0 7.5 high 0.20.0-1 22 Jan 2019
Buffer Overrun Vulnerability in OpenSC Package: CVE-2023-2977 7.1 high 0.21.0-1+deb11u1 01 Jun 2023
Buffer Overflow Vulnerability in OpenSC 6.8 medium 0.19.0~rc1-1 03 Sep 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About opensc

Is opensc safe to use?

Vulert records 97 vulnerabilities for opensc in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 97 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does opensc have?

97 vulnerabilities are recorded for opensc in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 97 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new opensc vulnerabilities disclosed?

2 vulnerabilities were recorded for opensc in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of opensc are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor opensc for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the opensc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.