Skip to main content
VulnerabilityPublished

CVE-2026-74049: Apache Tomcat · Jasper JSTL <c:redirect> plug-in implementation omits page abort (SKIP_PAGE)

Affects tomcatSource GCVE Database

0
Compare
Authoritative record:CVE-2026-74049· High

Not known to be exploited · fixed in 11.0.27 : patch tomcat soon.

Data as of 29 Oct 2026, 14:41 UTC

Severity
High

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

EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.27, 10.1.61, 9.0.123

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Oct 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 29 Oct 2026.

What to do

Upgrade tomcat to 11.0.27, 10.1.61 or 9.0.123.

Affected software

ProductAffectedFixed in
Bitnamitomcatpkg:bitnami/tomcatOther threatsAffected
  • >=7.0.0 <9.0.123
  • >=10.1.0 <10.1.61
  • >=11.0.0 <11.0.27
Fixed in
  • 9.0.123
  • 10.1.61
  • 11.0.27

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 instances to versions 9.0.123, 10.1.61, or 11.0.27 where the issue is fixed. No other mitigation or temporary workaround is indicated.

Description

An Execution After Redirect (EAR) vulnerability exists in Apache Tomcat's Jasper JSTL <c:redirect> plug-in implementation, where the page abort (SKIP_PAGE) is omitted. This affects multiple versions of Apache Tomcat, including 7.0.0 through 9.0.122, 10.1.0 through 10.1.60, and 11.0.0 through 11.0.26. The issue is fixed in versions 9.0.123, 10.1.61, and 11.0.27.

References

Community reviews

Loading reviews…