Skip to main content
VulnerabilityPublished

CVE-2026-118028: Apache Tomcat · Execution After Redirect (EAR) Vulnerability

Affects tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-118028· Medium

Not known to be exploited · fixed in 11.0.28 : update tomcat when convenient.

Data as of 20 Nov 2026, 01:39 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 11.0.28, 10.1.62, 9.0.124

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade org.apache.tomcat/tomcat to 11.0.28, 10.1.62 or 9.0.124.

Affected software

ProductAffectedFixed in
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • >=11.0.0-M18 <11.0.28
  • >=10.1.20 <10.1.62
  • >=9.0.87 <9.0.124
  • =8.5.100
Fixed in
  • 11.0.28
  • 10.1.62
  • 9.0.124

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

AI-suggested

Users should upgrade affected Apache Tomcat installations to versions 11.0.28, 10.1.62, or 9.0.124 where the vulnerability has been fixed. No other mitigation or temporary workaround is indicated in the available information.

Description

An Execution After Redirect (EAR) vulnerability exists in Apache Tomcat's RedirectValve component affecting specific flags. This vulnerability impacts Apache Tomcat versions from 11.0.0-M18 through 11.0.27, 10.1.20 through 10.1.61, 9.0.87 through 9.0.123, and version 8.5.100. The issue has been fixed in versions 11.0.28, 10.1.62, and 9.0.124. Users are advised to upgrade to these fixed versions to mitigate the vulnerability.

References

Community reviews

Loading reviews…