CVE-2026-18531

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-05. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

IBM Maximo Application Suite 9.2, 9.1, and 9.0 could allow a remote attacker to tamper with session data due to the use of a weak HMAC session signing secret.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

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

Security Bulletin: IBM MAS uses axios-1.15.2, protobufjs-8.0.1 and undici-7.26 which is vulnerable to multiple CVEs, and contains vulnerabilities related to missing Secure attribute on mas-redirect-uri cookie and weak HMAC Session Secret

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

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

Frequently asked(5)

What is CVE-2026-18531?
CVE-2026-18531 is a medium vulnerability published on August 5, 2026. IBM Maximo Application Suite 9.2, 9.1, and 9.0 could allow a remote attacker to tamper with session data due to the use of a weak HMAC session signing secret.
When was CVE-2026-18531 disclosed?
CVE-2026-18531 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 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-18531 actively exploited?
CVE-2026-18531 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 68.9% of all scored CVEs.
What is the CVSS score of CVE-2026-18531?
CVE-2026-18531 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-18531?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18531, 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-18531

Explore →

Is Your Infrastructure Affected by CVE-2026-18531?

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

Start Free Scan →Browse All CVEs