Security Resilience

CVE-2026-4820

Ibm Maximo Application Suite 8.10 – 8.10.33

Published
01 April 2026
Modified
07 April 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0019 8th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS 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

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

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
T1689 Downgrade Attack Defense Impairment
Adversaries may downgrade or use a version of system features that may be outdated, vulnerable, and/or does not support updated security controls.
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-27861Same product: Ibm Maximo Application Suite
CVE-2024-35150Same product: Ibm Maximo Application Suite
CVE-2025-14684Same product: Ibm Maximo Application Suite
CVE-2024-38314Same product: Ibm Maximo Application Suite
CVE-2025-1500Same product: Ibm Maximo Application Suite
CVE-2023-38723Same product: Ibm Maximo Application Suite
CVE-2024-35145Same product: Ibm Maximo Application Suite
CVE-2024-35146Same product: Ibm Maximo Application Suite
CVE-2024-35144Same product: Ibm Maximo Application Suite
CVE-2024-35148Same product: Ibm Maximo Application Suite

Affected Assets

ibm
maximo application suite
8.10 — 8.10.33 · 8.11 — 8.11.30 · 9.0 — 9.0.19

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • 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.

PR.DS-02 full match
blocks

Encryption of data-in-transit directly prevents cleartext transmission while the control also addresses integrity and availability.

PR.PS-01 mostly match
blocks

Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.

PR.PS-06 mostly match
blocks

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.

blocks

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).

blocks

Mandating cryptographic protection and stronger authentication on public networks stops the transmission of plaintext sensitive information.

removes

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.

prevents

Secure coding practices directly prevent missing the Secure attribute on sensitive cookies, though the control covers many other coding issues.

removes

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.

References