CVE-2026-10275

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-01. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw has been found in OpenSC up to 0.26.1. This affects the function test_kpgen_certwrite of the file src/tools/pkcs11-tool.c of the component pkcs11-tool Key Generation Module. This manipulation causes buffer overflow. The attack is possible to be carried out remotely. The complexity of an attack is rather high. It is indicated that the exploitability is difficult. The exploit has been published and may be used. Patch name: 814f745b3b6d100295f65f1935edd33d520d33ab. It is recommended to apply a patch to fix this issue.

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
23(Track)
EG Risk 23/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 computed
Severity50% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jun 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

GitHub - OpenSC/OpenSC: Open source smart card tools and middleware. PKCS#11/MiniDriver · GitHub

https://github.com/OpenSC/OpenSC/
github_commit

commit 814f745b3b6d (OpenSC/OpenSC)

Fix landed in OpenSC/OpenSC commit 814f745b3b6d — awaiting tagged release

https://github.com/OpenSC/OpenSC/commit/814f745b3b6d100295f65f1935edd33d520d33ab
generic

百度网盘 请输入提取码

https://pan.baidu.com/s/1nrZPKDz2eAcCpsaFiIRlrg
github_pr

pkcs11-tool: prevent buffer overflow

Fix merged in OpenSC/OpenSC PR #3684 on 2026-05-15 — awaiting tagged release

https://github.com/OpenSC/OpenSC/pull/3684
generic

OpenSC pkcs11-tool Global Buffer Overflow Vulnerability Report · Issue #3682 · OpenSC/OpenSC · GitHub

https://github.com/OpenSC/OpenSC/issues/3682

Vendor Advisories for CVE-2026-10275(2)

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)
PackageVulnerable rangeFixed inDependents
opensc0.21.0-1 ... 0.27.1-2 (23 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
opensc0.23.0-0.3 ... 0.27.1-2 (18 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
opensc0.26.1-2 ... 0.27.1-2 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
opensc0.26.1-2, 0.26.1-3, 0.27.0~rc1-1, 0.27.0~rc2-1, 0.27.1-10.27.1-2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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.

Showing the most recent 100 of 234 total refreshes for this CVE.

  1. 2026-09-16 05:14 UTCEPSS rescore
  2. 2026-09-14 06:08 UTCEG score recompute
  3. 2026-09-14 06:08 UTCVendor advisory
  4. 2026-09-14 06:08 UTCGHSA enrichment
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-13 00:06 UTCOSV refresh
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:21 UTCEPSS rescore
  20. 2026-08-28 21:40 UTCEPSS rescore
  21. 2026-08-27 14:24 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-25 03:52 UTCEG score recompute
  24. 2026-08-25 03:52 UTCGHSA enrichment
  25. 2026-08-23 13:53 UTCEG score recompute
Show 75 more
  1. 2026-08-23 13:53 UTCVendor advisory
  2. 2026-08-23 13:53 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:48 UTCEPSS rescore
  5. 2026-08-21 14:51 UTCEG score recompute
  6. 2026-08-21 14:51 UTCVendor advisory
  7. 2026-08-21 14:51 UTCGHSA enrichment
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 10:16 UTCEG score recompute
  10. 2026-08-20 10:16 UTCVendor advisory
  11. 2026-08-20 10:16 UTCGHSA enrichment
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 04:50 UTCEG score recompute
  15. 2026-08-17 04:50 UTCVendor advisory
  16. 2026-08-17 04:50 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:21 UTCEG score recompute
  19. 2026-08-16 02:21 UTCVendor advisory
  20. 2026-08-16 02:21 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 21:58 UTCVendor advisory
  24. 2026-08-14 21:58 UTCGHSA enrichment
  25. 2026-08-13 23:20 UTCEG score recompute
  26. 2026-08-13 23:20 UTCVendor advisory
  27. 2026-08-13 23:20 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-12 13:50 UTCEPSS rescore
  30. 2026-08-12 13:48 UTCEG score recompute
  31. 2026-08-12 13:48 UTCVendor advisory
  32. 2026-08-12 13:48 UTCGHSA enrichment
  33. 2026-08-11 13:42 UTCEPSS rescore
  34. 2026-08-11 13:35 UTCEG score recompute
  35. 2026-08-11 13:35 UTCVendor advisory
  36. 2026-08-11 13:35 UTCGHSA enrichment
  37. 2026-08-10 23:59 UTCEPSS rescore
  38. 2026-08-10 14:57 UTCGHSA enrichment
  39. 2026-08-09 16:18 UTCEG score recompute
  40. 2026-08-09 16:18 UTCVendor advisory
  41. 2026-08-09 16:18 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-08 17:40 UTCEG score recompute
  44. 2026-08-08 17:40 UTCVendor advisory
  45. 2026-08-08 17:40 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 18:44 UTCEG score recompute
  48. 2026-08-07 18:44 UTCGHSA enrichment
  49. 2026-08-06 19:54 UTCEG score recompute
  50. 2026-08-06 19:54 UTCVendor advisory
  51. 2026-08-06 19:54 UTCGHSA enrichment
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-05 21:16 UTCEG score recompute
  54. 2026-08-05 21:16 UTCVendor advisory
  55. 2026-08-05 21:16 UTCGHSA enrichment
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 22:39 UTCEG score recompute
  58. 2026-08-04 22:39 UTCVendor advisory
  59. 2026-08-04 22:39 UTCGHSA enrichment
  60. 2026-08-04 15:09 UTCEPSS rescore
  61. 2026-08-04 10:38 UTCEPSS rescore
  62. 2026-08-03 15:50 UTCEG score recompute
  63. 2026-08-03 15:50 UTCGHSA enrichment
  64. 2026-08-03 10:35 UTCEPSS rescore
  65. 2026-08-02 12:25 UTCEG score recompute
  66. 2026-08-02 12:25 UTCVendor advisory
  67. 2026-08-02 12:25 UTCGHSA enrichment
  68. 2026-08-02 02:26 UTCEPSS rescore
  69. 2026-08-01 13:36 UTCEG score recompute
  70. 2026-08-01 13:36 UTCVendor advisory
  71. 2026-08-01 13:36 UTCGHSA enrichment
  72. 2026-08-01 04:15 UTCEPSS rescore
  73. 2026-07-31 05:42 UTCEG score recompute
  74. 2026-07-31 05:42 UTCVendor advisory
  75. 2026-07-31 05:42 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-10275?
CVE-2026-10275 is a medium vulnerability published on June 1, 2026. A flaw has been found in OpenSC up to 0.26.1. This affects the function testkpgencertwrite of the file src/tools/pkcs11-tool.c of the component pkcs11-tool Key Generation Module. This manipulation causes buffer overflow. The attack is possible to be carried out remotely. The complexity of an attack…
When was CVE-2026-10275 disclosed?
CVE-2026-10275 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10275 actively exploited?
CVE-2026-10275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-10275?
CVE-2026-10275 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-10275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10275, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10275

Explore →

Is Your Infrastructure Affected by CVE-2026-10275?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs