CVE-2026-18669

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM 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(medium)
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
43%
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 24× in last 7d / 111× 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.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-09-19 12:04 UTCGHSA enrichment
  2. 2026-09-19 00:24 UTCEG score recompute
  3. 2026-09-19 00:24 UTCGHSA enrichment
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-18 12:54 UTCGHSA enrichment
  6. 2026-09-18 00:32 UTCEG score recompute
  7. 2026-09-18 00:32 UTCGHSA enrichment
  8. 2026-09-17 12:16 UTCGHSA enrichment
  9. 2026-09-17 00:21 UTCEG score recompute
  10. 2026-09-17 00:21 UTCGHSA enrichment
  11. 2026-09-16 14:07 UTCEPSS rescore
  12. 2026-09-16 12:45 UTCEG score recompute
  13. 2026-09-16 12:45 UTCGHSA enrichment
  14. 2026-09-16 05:14 UTCEPSS rescore
  15. 2026-09-16 01:14 UTCGHSA enrichment
  16. 2026-09-15 13:12 UTCEG score recompute
  17. 2026-09-15 13:12 UTCGHSA enrichment
  18. 2026-09-15 00:54 UTCGHSA enrichment
  19. 2026-09-14 13:23 UTCGHSA enrichment
  20. 2026-09-14 01:52 UTCEG score recompute
  21. 2026-09-14 01:52 UTCGHSA enrichment
  22. 2026-09-13 16:46 UTCEPSS rescore
  23. 2026-09-13 14:21 UTCGHSA enrichment
  24. 2026-09-13 02:51 UTCGHSA enrichment
  25. 2026-09-12 15:20 UTCEG score recompute
Show 75 more
  1. 2026-09-12 15:20 UTCGHSA enrichment
  2. 2026-09-12 15:00 UTCEPSS rescore
  3. 2026-09-12 03:49 UTCEG score recompute
  4. 2026-09-12 03:48 UTCGHSA enrichment
  5. 2026-09-11 16:17 UTCEG score recompute
  6. 2026-09-11 16:17 UTCGHSA enrichment
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:36 UTCEPSS rescore
  9. 2026-09-11 04:29 UTCGHSA enrichment
  10. 2026-09-10 16:58 UTCEG score recompute
  11. 2026-09-10 16:58 UTCGHSA enrichment
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-10 05:24 UTCGHSA enrichment
  14. 2026-09-09 17:52 UTCGHSA enrichment
  15. 2026-09-09 05:14 UTCEG score recompute
  16. 2026-09-09 05:14 UTCGHSA enrichment
  17. 2026-09-08 22:00 UTCEPSS rescore
  18. 2026-09-08 04:14 UTCGHSA enrichment
  19. 2026-09-07 16:43 UTCEG score recompute
  20. 2026-09-07 16:43 UTCGHSA enrichment
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 23:29 UTCEG score recompute
  23. 2026-09-06 23:29 UTCGHSA enrichment
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 11:58 UTCGHSA enrichment
  26. 2026-09-06 00:28 UTCEG score recompute
  27. 2026-09-06 00:28 UTCGHSA enrichment
  28. 2026-09-05 12:58 UTCGHSA enrichment
  29. 2026-09-05 12:55 UTCGHSA enrichment
  30. 2026-09-05 00:41 UTCEG score recompute
  31. 2026-09-05 00:41 UTCGHSA enrichment
  32. 2026-09-04 12:58 UTCEG score recompute
  33. 2026-09-04 12:58 UTCGHSA enrichment
  34. 2026-09-04 05:06 UTCEPSS rescore
  35. 2026-09-04 01:28 UTCGHSA enrichment
  36. 2026-09-03 12:45 UTCGHSA enrichment
  37. 2026-09-02 23:31 UTCEG score recompute
  38. 2026-09-02 23:31 UTCGHSA enrichment
  39. 2026-09-02 14:11 UTCEPSS rescore
  40. 2026-09-01 23:13 UTCEG score recompute
  41. 2026-09-01 23:13 UTCGHSA enrichment
  42. 2026-09-01 13:53 UTCEPSS rescore
  43. 2026-09-01 11:43 UTCEG score recompute
  44. 2026-09-01 11:43 UTCGHSA enrichment
  45. 2026-09-01 04:39 UTCEPSS rescore
  46. 2026-08-31 21:41 UTCGHSA enrichment
  47. 2026-08-31 07:32 UTCGHSA enrichment
  48. 2026-08-30 19:44 UTCEG score recompute
  49. 2026-08-30 19:44 UTCGHSA enrichment
  50. 2026-08-30 19:17 UTCEPSS rescore
  51. 2026-08-30 08:13 UTCEG score recompute
  52. 2026-08-30 08:13 UTCGHSA enrichment
  53. 2026-08-30 01:22 UTCEPSS rescore
  54. 2026-08-29 20:42 UTCGHSA enrichment
  55. 2026-08-29 08:35 UTCEG score recompute
  56. 2026-08-29 08:35 UTCGHSA enrichment
  57. 2026-08-28 21:41 UTCEPSS rescore
  58. 2026-08-28 04:09 UTCGHSA enrichment
  59. 2026-08-27 16:34 UTCEG score recompute
  60. 2026-08-27 16:34 UTCGHSA enrichment
  61. 2026-08-27 14:25 UTCEPSS rescore
  62. 2026-08-27 03:58 UTCGHSA enrichment
  63. 2026-08-26 16:28 UTCEG score recompute
  64. 2026-08-26 16:28 UTCGHSA enrichment
  65. 2026-08-26 14:46 UTCEPSS rescore
  66. 2026-08-26 04:15 UTCGHSA enrichment
  67. 2026-08-25 16:39 UTCEG score recompute
  68. 2026-08-25 16:39 UTCGHSA enrichment
  69. 2026-08-25 13:48 UTCEPSS rescore
  70. 2026-08-25 05:09 UTCGHSA enrichment
  71. 2026-08-24 17:38 UTCEG score recompute
  72. 2026-08-24 17:38 UTCGHSA enrichment
  73. 2026-08-24 06:07 UTCGHSA enrichment
  74. 2026-08-23 18:30 UTCGHSA enrichment
  75. 2026-08-23 06:59 UTCEG score recompute

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 57.4% 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.