CVE-2026-4870

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

IBM Qiskit SDK 0.43.0 through 2.5.0 could allow an attacker to trigger a segmentation fault leading to a denial of service due to uncontrolled recursion in the parser.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
18.5%
KEV
Not listed

Published

June 12, 2026

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

Security Bulletin: Qiskit SDK is vulnerable to specific functions may recurse too deeply and overflow the available stack space, when encountering certain classical expressions.

https://www.ibm.com/support/pages/node/7276123

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 95× 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-12 05:46 UTCEPSS rescore
  2. 2026-07-12 03:57 UTCEG score recompute
  3. 2026-07-11 15:28 UTCEG score recompute
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 02:53 UTCEG score recompute
  7. 2026-07-10 13:05 UTCEG score recompute
  8. 2026-07-09 21:37 UTCEG score recompute
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 03:46 UTCEG score recompute
  12. 2026-07-08 15:17 UTCEG score recompute
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 02:31 UTCEG score recompute
  15. 2026-07-07 13:59 UTCEG score recompute
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 00:58 UTCEG score recompute
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 00:44 UTCEG score recompute
  21. 2026-07-05 12:15 UTCEG score recompute
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 23:46 UTCEG score recompute
  24. 2026-07-04 11:15 UTCEG score recompute
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 70 more
  1. 2026-07-03 22:46 UTCEG score recompute
  2. 2026-07-03 10:14 UTCEG score recompute
  3. 2026-07-02 21:39 UTCEG score recompute
  4. 2026-07-02 09:11 UTCEG score recompute
  5. 2026-07-01 20:39 UTCEG score recompute
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 08:08 UTCEG score recompute
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 19:39 UTCEG score recompute
  10. 2026-06-30 07:10 UTCEG score recompute
  11. 2026-06-29 18:42 UTCEG score recompute
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 06:12 UTCEG score recompute
  15. 2026-06-28 17:16 UTCEG score recompute
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:47 UTCEG score recompute
  20. 2026-06-27 16:18 UTCEG score recompute
  21. 2026-06-27 03:49 UTCEG score recompute
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 15:20 UTCEG score recompute
  24. 2026-06-26 02:52 UTCEG score recompute
  25. 2026-06-25 14:22 UTCEG score recompute
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 01:53 UTCEG score recompute
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-24 13:24 UTCEG score recompute
  30. 2026-06-24 00:46 UTCEG score recompute
  31. 2026-06-23 21:33 UTCEPSS rescore
  32. 2026-06-23 21:33 UTCEPSS rescore
  33. 2026-06-23 12:12 UTCEG score recompute
  34. 2026-06-22 23:42 UTCEG score recompute
  35. 2026-06-22 14:25 UTCEPSS rescore
  36. 2026-06-22 14:25 UTCEPSS rescore
  37. 2026-06-22 11:11 UTCEG score recompute
  38. 2026-06-21 22:30 UTCEG score recompute
  39. 2026-06-21 14:56 UTCEPSS rescore
  40. 2026-06-21 14:56 UTCEPSS rescore
  41. 2026-06-21 09:13 UTCEG score recompute
  42. 2026-06-21 01:59 UTCEPSS rescore
  43. 2026-06-21 01:59 UTCEPSS rescore
  44. 2026-06-20 20:22 UTCEG score recompute
  45. 2026-06-20 05:59 UTCEG score recompute
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-19 16:52 UTCEG score recompute
  49. 2026-06-19 04:20 UTCEG score recompute
  50. 2026-06-18 17:52 UTCEPSS rescore
  51. 2026-06-18 17:52 UTCEPSS rescore
  52. 2026-06-18 15:48 UTCEG score recompute
  53. 2026-06-18 03:12 UTCEG score recompute
  54. 2026-06-17 17:53 UTCEPSS rescore
  55. 2026-06-17 14:43 UTCEG score recompute
  56. 2026-06-17 02:13 UTCEG score recompute
  57. 2026-06-16 17:53 UTCEPSS rescore
  58. 2026-06-16 13:44 UTCEG score recompute
  59. 2026-06-16 01:09 UTCEG score recompute
  60. 2026-06-15 17:49 UTCEPSS rescore
  61. 2026-06-15 17:49 UTCEPSS rescore
  62. 2026-06-15 12:39 UTCEG score recompute
  63. 2026-06-15 00:11 UTCEG score recompute
  64. 2026-06-14 23:18 UTCEPSS rescore
  65. 2026-06-14 11:42 UTCEG score recompute
  66. 2026-06-13 23:12 UTCEG score recompute
  67. 2026-06-13 23:00 UTCEPSS rescore
  68. 2026-06-13 10:43 UTCEG score recompute
  69. 2026-06-12 22:14 UTCEG score recompute
  70. 2026-06-12 22:13 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-4870?
CVE-2026-4870 is a high vulnerability published on June 12, 2026. IBM Qiskit SDK 0.43.0 through 2.5.0 could allow an attacker to trigger a segmentation fault leading to a denial of service due to uncontrolled recursion in the parser.
When was CVE-2026-4870 disclosed?
CVE-2026-4870 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4870 actively exploited?
CVE-2026-4870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4870?
CVE-2026-4870 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-4870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4870, 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-4870

Explore →

Is Your Infrastructure Affected by CVE-2026-4870?

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

Start Free Scan →Browse All CVEs