CVE-2026-40510

MEDIUMNVD 6.83.8▼
EchelonGraph scoreMEDIUM confidence

Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-05-29. NVD baseline CVSS 6.8; sources differ by 3.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: NoneExposed: 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
3.8(medium)
EPSS
12.0%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 14, 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 14× in last 7d / 51× 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.

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

Related CVEs(same CWE)

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 14, 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 12.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40510?
CVE-2026-40510 has a CVSS v3 base score of 6.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 3.8.
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.

Start Free Scan →Browse All CVEs