VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

opensc: vulnerability history, versions and safety

opensc is a package in the OSS-Fuzz ecosystem. Vulert records 84 vulnerabilities for it across 19 releases, from Jun 2020 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
84 vulnerabilities recorded H20 M52 U12
i
3 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 06 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: 3 of the 84 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 84 vulnerabilities on record across 5 years, 2 in the last year.

What to do: Plan around the 3 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 84 over 5 years · 2 in the last year i
  • Latest disclosure 06 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 3 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.

i
Version Vulert vulnerabilities Fix published Details
0.26.1 H1 M1 U1 No Details →
0.26.0 H1 M1 U1 No Details →
0.26.0-rc1 H1 M1 U1 No Details →
0.25.1 H1 M1 U1 No Details →
0.25.0 H1 M1 U1 No Details →
0.25.0-rc1 H1 M1 U1 No Details →
0.24.0 H2 M1 U1 No Details →
0.24.0-rc2 H1 M2 U1 No Details →
0.24.0-rc1 H1 M4 U2 No Details →
0.23.0 H2 M3 U1 No Details →
0.23.0-rc2 H2 M4 U1 No Details →
0.23.0-rc1 H4 M5 U1 No Details →
0.22.0-rc2 H1 M1 Yes Details →
0.22.0-rc1 H1 M1 Yes Details →
0.21.0 H1 M5 U2 Yes Details →
0.21.0-rc2 H1 M6 U2 Yes Details →
0.21.0-rc1 H1 M7 U2 Yes Details →
0.20.0-rc4 H1 M1 Yes Details →
0.20.0-rc1 H1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 27
  • 2021 6
  • 2022 29
  • 2023 19
  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for opensc

The 5 most severe of 84 vulnerabilities recorded for this package

Search all 84 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in cosm_new_file in opensc N/A high 089cedc7520fbb9e0e4a912c4c3866a1aa429de6 26 Mar 2022
OpenSC: Segv on unknown address in sc_file_clear_acl_entries N/A unrated 8697a01850d5e02a3099acd5160d0a0ee2d31077 24 Mar 2022
Stack-use-after-return in template_sanity_check in opensc N/A unrated 8697a01850d5e02a3099acd5160d0a0ee2d31077 21 Mar 2022
Negative-size-param vulnerability in opensc N/A unrated fe6864c5f3ba9085acdac569b7567b911e01f445 19 Dec 2020
Critical UNKNOWN READ Vulnerability in OpenSC Package N/A medium 39e8771238adf2e3ea0c3b23285b6825a8feaceb 06 Jun 2026

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 84 vulnerabilities for opensc in OSS-Fuzz: 0 critical, 20 high, 52 medium and 0 low, plus 12 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does opensc have?

84 vulnerabilities are recorded for opensc in the OSS-Fuzz ecosystem: 0 critical, 20 high, 52 medium and 0 low, plus 12 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 24 Jun 2020. 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.