CVE-2026-19795

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

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

Qiskit could allow a local attacker to cause a denial of service due to a stack overflow during deserialization of QPY payloads. A malicious QPY payload can trigger a segmentation fault, causing the application to crash when deserializing untrusted input.

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

Published

September 3, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

Security Bulletin: Qiskit SDK is vulnerable when deserializing QPY Files and may overflow the available stack space.

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 31× 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-09-20 12:31 UTCEG score recompute
  2. 2026-09-19 12:26 UTCEG score recompute
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 12:44 UTCEG score recompute
  5. 2026-09-17 13:01 UTCEG score recompute
  6. 2026-09-16 14:07 UTCEPSS rescore
  7. 2026-09-16 13:06 UTCEG score recompute
  8. 2026-09-16 05:14 UTCEPSS rescore
  9. 2026-09-15 13:24 UTCEG score recompute
  10. 2026-09-14 13:42 UTCEG score recompute
  11. 2026-09-13 16:46 UTCEPSS rescore
  12. 2026-09-13 13:52 UTCEG score recompute
  13. 2026-09-12 15:00 UTCEPSS rescore
  14. 2026-09-12 14:10 UTCEG score recompute
  15. 2026-09-11 14:52 UTCEPSS rescore
  16. 2026-09-11 14:27 UTCEG score recompute
  17. 2026-09-11 09:36 UTCEPSS rescore
  18. 2026-09-10 14:44 UTCEG score recompute
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-09 15:01 UTCEG score recompute
  21. 2026-09-08 22:00 UTCEPSS rescore
  22. 2026-09-06 20:53 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 21:10 UTCEG score recompute
  25. 2026-09-04 21:28 UTCEG score recompute
Show 6 more
  1. 2026-09-04 20:27 UTCEG score recompute
  2. 2026-09-04 14:21 UTCEG score recompute
  3. 2026-09-04 13:46 UTCEG score recompute
  4. 2026-09-03 20:23 UTCEG score recompute
  5. 2026-09-03 20:04 UTCEG score recompute
  6. 2026-09-03 20:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19795?
CVE-2026-19795 is a medium vulnerability published on September 3, 2026. Qiskit could allow a local attacker to cause a denial of service due to a stack overflow during deserialization of QPY payloads. A malicious QPY payload can trigger a segmentation fault, causing the application to crash when deserializing untrusted input.
When was CVE-2026-19795 disclosed?
CVE-2026-19795 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19795 actively exploited?
CVE-2026-19795 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-19795?
CVE-2026-19795 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-19795?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19795, 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-19795

Explore →

Is Your Infrastructure Affected by CVE-2026-19795?

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