CVE-2026-10027

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

IBM MQ could allow a remote attacker to cause a denial of service or execute arbitrary code due to a buffer overflow when processing malformed compressed data on channels configured with compression enabled.

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

Published

September 18, 2026

Last Modified

September 23, 2026

Advisory Details (1)

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

Security Bulletin: IBM MQ queue manager is vulnerable to unauthenticated remote code execution (CVE-2026-10027)

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

Vendor Advisories for CVE-2026-10027(1)

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 39× in last 7d / 39× 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-25 09:15 UTCGHSA enrichment
  2. 2026-09-25 05:27 UTCGHSA enrichment
  3. 2026-09-25 01:39 UTCGHSA enrichment
  4. 2026-09-24 21:50 UTCGHSA enrichment
  5. 2026-09-24 18:01 UTCEG score recompute
  6. 2026-09-24 18:01 UTCGHSA enrichment
  7. 2026-09-24 13:41 UTCGHSA enrichment
  8. 2026-09-24 09:53 UTCGHSA enrichment
  9. 2026-09-24 06:05 UTCGHSA enrichment
  10. 2026-09-24 02:16 UTCGHSA enrichment
  11. 2026-09-23 22:28 UTCGHSA enrichment
  12. 2026-09-23 18:40 UTCEG score recompute▲ 1.70
  13. 2026-09-23 18:40 UTCGHSA enrichment
  14. 2026-09-23 18:37 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  15. 2026-09-23 13:47 UTCEPSS rescore
  16. 2026-09-23 13:39 UTCGHSA enrichment
  17. 2026-09-23 01:34 UTCEG score recompute
  18. 2026-09-23 01:34 UTCGHSA enrichment
  19. 2026-09-22 13:29 UTCGHSA enrichment
  20. 2026-09-22 01:24 UTCEG score recompute
  21. 2026-09-22 01:24 UTCGHSA enrichment
  22. 2026-09-21 13:19 UTCEG score recompute
  23. 2026-09-21 13:19 UTCGHSA enrichment
  24. 2026-09-21 12:55 UTCEG score recompute
  25. 2026-09-21 12:55 UTCGHSA enrichment
Show 14 more
  1. 2026-09-21 04:53 UTCEG score recompute
  2. 2026-09-21 04:53 UTCGHSA enrichment
  3. 2026-09-20 20:15 UTCEPSS rescore
  4. 2026-09-20 16:45 UTCGHSA enrichment
  5. 2026-09-20 04:40 UTCGHSA enrichment
  6. 2026-09-19 16:35 UTCEG score recompute
  7. 2026-09-19 16:35 UTCGHSA enrichment
  8. 2026-09-19 04:31 UTCEG score recompute
  9. 2026-09-19 04:30 UTCGHSA enrichment
  10. 2026-09-19 04:01 UTCEG score recompute
  11. 2026-09-19 04:01 UTCGHSA enrichment
  12. 2026-09-18 16:26 UTCEG score recompute
  13. 2026-09-18 15:51 UTCEG score recompute
  14. 2026-09-18 15:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10027?
CVE-2026-10027 is a critical vulnerability published on September 18, 2026. IBM MQ could allow a remote attacker to cause a denial of service or execute arbitrary code due to a buffer overflow when processing malformed compressed data on channels configured with compression enabled.
When was CVE-2026-10027 disclosed?
CVE-2026-10027 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10027 actively exploited?
CVE-2026-10027 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 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-10027?
CVE-2026-10027 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-10027?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10027, 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-10027

Explore →

Is Your Infrastructure Affected by CVE-2026-10027?

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

Book a Demo →Browse All CVEs