CVE-2026-4820 json
IBM Maximo Application Suite was vulnerable to because Cookie ltpatoken2_<workspace_name> was not set with secure flag
published 2026-04-01 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-18068
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
IBM Maximo Application Suite 9.1, 9.0, 8.11, and 8.10 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.
Patch / fix
- ibm maximo_application_suite 8.10.33, 8.11.30, 9.0.19, 9.1.8
- ibm.com/support/pages/node/7268028 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa vex VA-26-097-02 updated cvss 4.3
IBM Maximo Application Suite Sensitive Tokens without 'Secure' Attribute
-
IBM Maximo Application Suite 9.1.0, 9.0, 8.11.0, 8.10affected: vendor fix ibm.com
-
IBM Maximo Application Suite 9.1.8, 9.0.19, 8.11.30, 8.10.33fixed: vendor fix ibm.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N |
Affected products
- IBM Maximo Application Suite
Classification
References
-
ibm.com
/support/pages/node/7268028
vendor-advisory, patch
Sources
- CVE List CVE-2026-4820
- NVD CVE-2026-4820
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.