CVE-2026-53404: Apache Tomcat: Bad ornext processing in RewriteValve
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Apache Software Foundation Apache Tomcat 11.0.23.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Apache Software Foundation Apache Tomcat 11.0.23 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat's rewrite valve meant that if the first condition in an OR chain matched, subsequent non-OR conditions were skipped. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119, which fix the issue.
- BDU:2026-11859
- GHSA-h792-v28v-ppgr
- ALSA-2026:68651
- ALSA-2026:68660
- openSUSE-SU-2026:11195-1
- openSUSE-SU-2026:11208-1
- openSUSE-SU-2026:11209-1
- openSUSE-SU-2026:21327-1
- openSUSE-SU-2026:21328-1
- openSUSE-SU-2026:21329-1
- RHSA-2026:29203
- RHSA-2026:32960
- RHSA-2026:43401
- RHSA-2026:49951
- RHSA-2026:68651
- RHSA-2026:68660
- SUSE-SU-2026:22646-1
- SUSE-SU-2026:22647-1
- SUSE-SU-2026:22648-1
- SUSE-SU-2026:3087-1
- Published
- Jun 29, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-670
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | tomcat | cpe:2.3:a:apache:tomcat |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Tomcat
- 11.0.0-M1 and later · up to and including 11.0.22affected · semver
- 10.1.0-M1 and later · up to and including 10.1.55affected · semver
- 9.0.0.M1 and later · up to and including 9.0.118affected · semver
- 8.5.0 and later · up to and including 8.5.100affected · semver
- before 8.0.0not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache tomcat8.5.0 and later · up to 8.5.100 inclusive
- apache tomcat9.0.0 and later · before 9.0.119
- apache tomcat10.1.0 and later · before 10.1.56
- apache tomcat11.0.0 and later · before 11.0.23
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | tomcat9 | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-admin-webapps | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-docs-webapp | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-el-3.0-api | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-jsp-2.3-api | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-lib | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-servlet-4.0-api | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:10 | tomcat9-webapps | before 1:9.0.120-1.el10_2.alma.1 | 1:9.0.120-1.el10_2.alma.1 |
| AlmaLinux:9 | tomcat | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-admin-webapps | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-docs-webapp | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-el-3.0-api | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-jsp-2.3-api | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-lib | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-servlet-4.0-api | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| AlmaLinux:9 | tomcat-webapps | before 1:9.0.120-2.el9_8 | 1:9.0.120-2.el9_8 |
| Debian:12 | tomcat10 | before 10.1.60-1~deb12u1 | 10.1.60-1~deb12u1 |
| Debian:12 | tomcat9 | before 9.0.70-2 | 9.0.70-2 |
| Debian:13 | tomcat10 | before 10.1.60-1~deb13u1 | 10.1.60-1~deb13u1 |
| Debian:13 | tomcat11 | from 0 | — |
| Debian:14 | tomcat10 | before 10.1.60-1 | 10.1.60-1 |
| Debian:14 | tomcat11 | before 11.0.24-1 | 11.0.24-1 |
| Maven | org.apache.tomcat:tomcat | from 10.1.0-M1 · before 10.1.56 | 10.1.56 |
| Maven | org.apache.tomcat:tomcat | from 11.0.0-M1 · before 11.0.23 | 11.0.23 |
+96
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV99Now
- CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x…KEV96Now
- CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV92Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43515May 12, 2026 · Apache Tomcat: Security constraints not correctly applied36Monitor
- ← EarlierCVE-2026-50229Jun 29, 2026 · Apache Tomcat: XSS in number guess example25Monitor
- Later →CVE-2026-53434Jun 29, 2026 · Apache Tomcat: Invalid CRL configuration doesn't trigger failure for FFM Connector36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Apache Software Foundation Apache Tomcat | 11.0.23 · description | Vendor (CNA) |
| almalinux:tomcat | 1:9.0.120-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:tomcat-admin-webapps | 1:9.0.120-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:tomcat-docs-webapp | 1:9.0.120-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:tomcat-el-3.0-api | 1:9.0.120-2.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:tomcat9 | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-admin-webapps | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-docs-webapp | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-el-3.0-api | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-jsp-2.3-api | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-lib | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-servlet-4.0-api | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:tomcat9-webapps | 1:9.0.120-1.el10_2.alma.1 · AlmaLinux:10 | Package registry (OSV) |
| debian:tomcat10 | 10.1.60-1 · Debian:14 | Package registry (OSV) |
| debian:tomcat10 | 10.1.60-1~deb12u1 · Debian:12 | Package registry (OSV) |
| debian:tomcat11 | 11.0.24-1 · Debian:14 | Package registry (OSV) |
| debian:tomcat9 | 9.0.70-2 · Debian:12 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat | 10.1.56 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat | 11.0.23 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat | 9.0.119 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat-catalina | 10.1.56 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat-catalina | 11.0.23 | Package registry (OSV) |
| Maven:org.apache.tomcat:tomcat-catalina | 9.0.119 | Package registry (OSV) |
| Maven:org.apache.tomcat.embed:tomcat-embed-core | 10.1.56 | Package registry (OSV) |
| Maven:org.apache.tomcat.embed:tomcat-embed-core | 11.0.23 | Package registry (OSV) |
| Maven:org.apache.tomcat.embed:tomcat-embed-core | 9.0.119 | Package registry (OSV) |
| opensuse:tomcat | 9.0.119-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:tomcat10 | 10.1.56-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:tomcat11 | 11.0.23-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jws6-tomcat | 0:10.1.49-15.redhat_00013.1.el10jws · Red Hat:jboss_enterprise_web_server:6.2::el10 | Package registry (OSV) |
+36
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-552760 days apartApache Tomcat: Logged effective web.xml is incomplete36Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0464 · Jun 30, 2026(Apache Tomcat Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-670 · Always-Incorrect Control Flow ImplementationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.