Apache Tomcat cache exposure of sensitive data in ExpiresFilter
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
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
Original 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 systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- Apache Software Foundation Apache TomcatFrom 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
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread.html/dtgwcln115k2tdjj2kxctlwq3584qgj8 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-121649 |
| Record | NVD · CVE-2026-121649 |
Questions about CVE-2026-121649
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: cve.now feed data
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: cve.now feed data
Related
- CVE-2026-103119Apache Tomcat: AJP response mix-up
- CVE-2026-101356Apache Tomcat: HTTP/2 request/response mix-up after error during async processing
- CVE-2026-101296Apache Tomcat: JNDIRealm bind credential validation fails open for non-GSSAPI SASL mechanisms
- CVE-2026-86246Apache Tomcat Native: Insecure OpenSSL options enabled
- CVE-2026-80353Apache Tomcat: TOCTOU when setting specific permissions for Unix Domain Sockets - Fix for CVE-2026-65183 did not address APR connector
- CVE-2026-93446Apache Tomcat: Possible TLS 1.3 connection failures
No corrections so far. Something wrong on this page? Report an error.