CVE-2026-40510

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

OpenSC before 0.27.0-rc1, fixed in commit 3f24f0b, contains a stack buffer overflow vulnerability in piv_process_history() in src/libopensc/card-piv.c that allows physically present attackers to trigger memory corruption by presenting a crafted PIV smart card or USB device returning a URL field longer than 118 bytes in the Key History Object ASN.1 response.

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

Published

May 29, 2026

Last Modified

July 21, 2026

Advisory Details (3)

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

OpenSC < 0.27.0-rc1 Stack Buffer Overflow via piv_process_history() in card-piv.c | Advisories | VulnCheck

https://www.vulncheck.com/advisories/opensc-stack-buffer-overflow-via-piv-process-history-in-card-piv-c
github_pr

card-piv.c - fix history object

Fix merged in OpenSC/OpenSC PR #3558 on 2026-01-26 — awaiting tagged release

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

commit 3f24f0b48a48 (OpenSC/OpenSC)

Fix landed in OpenSC/OpenSC commit 3f24f0b48a48 — awaiting tagged release

https://github.com/OpenSC/OpenSC/commit/3f24f0b48a481a8cf2e46059d8238a283ddc1c13

Vendor Advisories for CVE-2026-40510(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 53× 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 169 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40510?
CVE-2026-40510 is a medium vulnerability published on May 29, 2026. OpenSC before 0.27.0-rc1, fixed in commit 3f24f0b, contains a stack buffer overflow vulnerability in pivprocesshistory() in src/libopensc/card-piv.c that allows physically present attackers to trigger memory corruption by presenting a crafted PIV smart card or USB device returning a URL field…
When was CVE-2026-40510 disclosed?
CVE-2026-40510 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40510 actively exploited?
CVE-2026-40510 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 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-40510?
CVE-2026-40510 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-40510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40510, 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

Explore the affected products and dependency analysis for CVE-2026-40510

Explore →

Is Your Infrastructure Affected by CVE-2026-40510?

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