CVE-2026-4820
Ibm Maximo Application Suite 8.10 – 8.10.33
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-4820 is a medium-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in Ibm Maximo Application Suite. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-18068
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.1
Mitigating Controls (NIST 800-53 r5) AI
SC-8 directly requires protecting confidentiality of transmitted information, which structurally eliminates cleartext transmission of sensitive data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Encryption of data-in-transit directly prevents cleartext transmission while the control also addresses integrity and availability.
Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.
Secure SDLC practices explicitly require correct use of security attributes such as the cookie Secure flag.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.21 mandates identifying/implementing network service security features (explicitly including encryption and connection controls), formulating rules that cover authentication/authorization/monitoring/VPNs, and ensuring providers do the same; this stops cleartext transmission from being exploitable in the large majority of network channels, with a bounded remainder (e.g. internal non-networked flows or unaddressed legacy protocols).
Mandating cryptographic protection and stronger authentication on public networks stops the transmission of plaintext sensitive information.
A.5.17 mandates secure transmission of authentication information, removing cleartext transmission of that specific sensitive data, but does not address other sensitive information transmitted in cleartext, so it removes only a subset of CWE-319 instances.
Secure coding practices directly prevent missing the Secure attribute on sensitive cookies, though the control covers many other coding issues.
A.8.5 requires that passwords not be transmitted in cleartext, so applying it removes that specific instance of cleartext transmission, but it does not address other sensitive information sent in cleartext.