CVE-2026-53404VulnerabilityPublished 29 Jun 2026Updated 17 Oct 2026

Tomcat6: Always-Incorrect Control Flow Implementation vulnerability

Affects tomcat6Source GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2026-53404· High 7.3

Not known to be exploited · CVSS 7.3 High · fixed in 8.0.32-1ubuntu1.13+esm2 : patch tomcat6 soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.32-1ubuntu1.13+esm2, 8.5.39-1ubuntu1~18.04.3+esm6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Ubuntu tomcat8 to 8.0.32-1ubuntu1.13+esm2 (package) or 8.5.39-1ubuntu1~18.04.3+esm6 (package).

Patches and advisories

ubuntu.com/security/notices/USN-8551-1 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Ubuntu 26.10tomcat10`pkg:deb/ubuntu/tomcat10?arch=source&distro=stonking`Other threats	Affected 10.1.40-1ubuntu1 – 10.1.57~us1-0ubuntu1 7 affected builds	Fixed in–
Ubuntu 26.10tomcat11`pkg:deb/ubuntu/tomcat11?arch=source&distro=stonking`Other threats	Affected 11.0.18-1 – 11.0.24-1ubuntu1 5 affected builds	Fixed in–
Ubuntu 26.10tomcat9`pkg:deb/ubuntu/tomcat9?arch=source&distro=stonking`Other threats	Affected =9.0.115-1 =9.0.115-1ubuntu1 =9.0.118-1	Fixed in–
Ubuntu 26.04 LTStomcat10`pkg:deb/ubuntu/tomcat10?arch=source&distro=resolute`Other threats	Affected =10.1.40-1ubuntu1 =10.1.40-1ubuntu1.26.04.1 =10.1.55-1ubuntu2~26.04.1	Fixed in–
Ubuntu 26.04 LTStomcat9`pkg:deb/ubuntu/tomcat9?arch=source&distro=resolute`Other threats	Affected 9.0.95-1ubuntu1 – 9.0.118-1~26.04.1 5 affected builds	Fixed in–
Ubuntu 26.04 LTStomcat11`pkg:deb/ubuntu/tomcat11?arch=source&distro=resolute`Other threats	Affected 11.0.6-1 – 11.0.22-2ubuntu2~26.04.1 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…