CVE-2026-18669

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: 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 is vulnerable to a privilege escalation as the result of a remote code execution vulnerability in the activation engine component. An authenticated attacker can execute a maliciously planted script with root authority.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By A Privilege Escalation Vulnerability [CVE-2026-18669]

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

Vendor Advisories for CVE-2026-18669(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 27× in last 7d / 40× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:25 UTCGHSA enrichment
  3. 2026-08-20 09:54 UTCGHSA enrichment
  4. 2026-08-19 22:24 UTCEG score recompute
  5. 2026-08-19 22:24 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 10:49 UTCGHSA enrichment
  8. 2026-08-18 23:18 UTCEG score recompute
  9. 2026-08-18 23:18 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 11:45 UTCGHSA enrichment
  12. 2026-08-18 00:14 UTCEG score recompute
  13. 2026-08-18 00:14 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 12:42 UTCGHSA enrichment
  16. 2026-08-17 01:11 UTCEG score recompute
  17. 2026-08-17 01:11 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 13:40 UTCEG score recompute
  20. 2026-08-16 13:40 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-16 02:10 UTCGHSA enrichment
  23. 2026-08-15 14:40 UTCGHSA enrichment
  24. 2026-08-15 03:09 UTCEG score recompute
  25. 2026-08-15 03:09 UTCGHSA enrichment
Show 15 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 15:38 UTCGHSA enrichment
  3. 2026-08-14 04:08 UTCEG score recompute
  4. 2026-08-14 04:08 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 16:37 UTCGHSA enrichment
  7. 2026-08-13 08:30 UTCGHSA enrichment
  8. 2026-08-12 21:00 UTCGHSA enrichment
  9. 2026-08-12 20:20 UTCEG score recompute
  10. 2026-08-12 20:20 UTCGHSA enrichment
  11. 2026-08-12 19:46 UTCEG score recompute
  12. 2026-08-12 19:46 UTCGHSA enrichment
  13. 2026-08-12 18:18 UTCEG score recompute
  14. 2026-08-12 17:51 UTCEG score recompute
  15. 2026-08-12 17:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18669?
CVE-2026-18669 is a high vulnerability published on August 12, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 is vulnerable to a privilege escalation as the result of a remote code execution vulnerability in the activation engine component. An authenticated attacker can execute a maliciously planted script with root authority.
When was CVE-2026-18669 disclosed?
CVE-2026-18669 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18669 actively exploited?
CVE-2026-18669 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.5% of all scored CVEs.
What is the CVSS score of CVE-2026-18669?
CVE-2026-18669 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-18669?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18669, 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-18669

Explore →

Is Your Infrastructure Affected by CVE-2026-18669?

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

Start Free Scan →Browse All CVEs