CVE-2026-18175

HIGHNVD 7.58.1▲
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. NVD baseline CVSS 7.5; sources differ by 0.6.

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

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

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to manipulate database transactions due to improper authorization in the DDM target dispatcher.

CVSS v3
7.5
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 10, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Improper Authorization and Authentication Vulnerabilities in DDM / DRDA [CVE-2026-18175, CVE-2026-18221]

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

Vendor Advisories for CVE-2026-18175(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 23× in last 7d / 65× 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 05:39 UTCGHSA enrichment
  2. 2026-09-19 17:13 UTCEG score recompute
  3. 2026-09-19 17:12 UTCGHSA enrichment
  4. 2026-09-19 04:47 UTCEG score recompute
  5. 2026-09-19 04:47 UTCGHSA enrichment
  6. 2026-09-18 19:27 UTCEPSS rescore
  7. 2026-09-18 16:20 UTCGHSA enrichment
  8. 2026-09-18 03:55 UTCEG score recompute
  9. 2026-09-18 03:55 UTCGHSA enrichment
  10. 2026-09-17 15:30 UTCGHSA enrichment
  11. 2026-09-17 03:00 UTCEG score recompute
  12. 2026-09-17 03:00 UTCGHSA enrichment
  13. 2026-09-16 14:07 UTCEPSS rescore
  14. 2026-09-16 13:57 UTCEG score recompute
  15. 2026-09-16 13:57 UTCGHSA enrichment
  16. 2026-09-16 05:14 UTCEPSS rescore
  17. 2026-09-16 01:32 UTCGHSA enrichment
  18. 2026-09-15 13:07 UTCEG score recompute
  19. 2026-09-15 13:07 UTCGHSA enrichment
  20. 2026-09-15 00:42 UTCGHSA enrichment
  21. 2026-09-14 12:17 UTCGHSA enrichment
  22. 2026-09-13 23:52 UTCEG score recompute
  23. 2026-09-13 23:52 UTCGHSA enrichment
  24. 2026-09-13 16:46 UTCEPSS rescore
  25. 2026-09-13 11:27 UTCGHSA enrichment
Show 40 more
  1. 2026-09-12 23:02 UTCEG score recompute
  2. 2026-09-12 23:02 UTCGHSA enrichment
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-12 10:36 UTCGHSA enrichment
  5. 2026-09-11 22:11 UTCEG score recompute
  6. 2026-09-11 22:11 UTCGHSA enrichment
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:46 UTCEG score recompute
  9. 2026-09-11 09:46 UTCGHSA enrichment
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 21:21 UTCGHSA enrichment
  12. 2026-09-10 21:06 UTCEG score recompute
  13. 2026-09-10 21:06 UTCGHSA enrichment
  14. 2026-09-10 11:48 UTCEG score recompute
  15. 2026-09-10 11:48 UTCGHSA enrichment
  16. 2026-09-10 09:34 UTCEPSS rescore
  17. 2026-09-09 23:22 UTCGHSA enrichment
  18. 2026-09-09 08:22 UTCEG score recompute
  19. 2026-09-09 08:22 UTCGHSA enrichment
  20. 2026-09-08 22:00 UTCEPSS rescore
  21. 2026-09-08 19:57 UTCEG score recompute
  22. 2026-09-08 19:57 UTCGHSA enrichment
  23. 2026-09-08 19:50 UTCNVD updateCVSS v3 → 7.5
  24. 2026-09-08 15:14 UTCGHSA enrichment
  25. 2026-09-08 08:27 UTCGHSA enrichment
  26. 2026-09-07 20:02 UTCEG score recompute
  27. 2026-09-07 20:02 UTCGHSA enrichment
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-07 07:37 UTCGHSA enrichment
  30. 2026-09-06 19:09 UTCEG score recompute
  31. 2026-09-06 19:09 UTCGHSA enrichment
  32. 2026-09-06 13:47 UTCEPSS rescore
  33. 2026-09-06 06:43 UTCGHSA enrichment
  34. 2026-09-05 18:18 UTCEG score recompute
  35. 2026-09-05 18:17 UTCGHSA enrichment
  36. 2026-09-05 05:53 UTCEG score recompute
  37. 2026-09-05 05:53 UTCGHSA enrichment
  38. 2026-09-04 17:28 UTCEG score recompute
  39. 2026-09-04 16:29 UTCEG score recompute
  40. 2026-09-04 16:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18175?
CVE-2026-18175 is a high vulnerability published on September 4, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to manipulate database transactions due to improper authorization in the DDM target dispatcher.
When was CVE-2026-18175 disclosed?
CVE-2026-18175 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18175 actively exploited?
CVE-2026-18175 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 90.8% of all scored CVEs.
What is the CVSS score of CVE-2026-18175?
CVE-2026-18175 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2026-18175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18175, 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-18175

Explore →

Is Your Infrastructure Affected by CVE-2026-18175?

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

Start Free Scan →Browse All CVEs