Quick answers
- Is CVE-2026-74049 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74049 being exploited in the wild.
- How severe is CVE-2026-74049?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Apache Tomcat 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, 9.0.0-M1 through 9.0.122, 8.5.0 through 8.5.100 (EOL), 7.0.0 through 7.0.109 (EOL).
- Is there a fix for CVE-2026-74049?
- Yes: fixed in 11.0.27, 10.1.61, 9.0.123. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74049 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-74049?
- Check whether you run Apache Tomcat at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 11.0.27, 10.1.61, 9.0.123
Technical details
An Execution After Redirect (EAR) vulnerability exists in Apache Tomcat where code may be executed after a redirect operation completes, potentially violating expected control flow. The vulnerability affects Tomcat 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, 9.0.0-M1 through 9.0.122, and end-of-life versions 8.5.0 through 8.5.100 and 7.0.0 through 7.0.109. Exploitation requires network access to the affected Tomcat instance.
Affected products
- Apache Tomcat 11.0.0-M1 through 11.0.26, 10.1.0-M1 through 10.1.60, 9.0.0-M1 through 9.0.122, 8.5.0 through 8.5.100 (EOL), 7.0.0 through 7.0.109 (EOL)
Timeline
- 2026-10-20: disclosed: CVE-2026-74049 published