CVE-2023-41080 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in org.apache.tomcat:tomcat. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.
Apache Tomcat: Open redirect with FORM authentication
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-41080.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-41080 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core+3 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in FORM authentication feature Apache Tomcat.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.0.12, from 9.0.0-M1 through 9.0.79 and from 8.5.0 through 8.5.92. Older, EOL versions may also be affected.
The vulnerability is limited to the ROOT (default) web application.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat | ≥ 11.0.0-M1&&< 11.0.0-M11 | 11.0.0-M11org.apache.tomcat:tomcat:11.0.0-M11 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 10.1.0-M1&&< 10.1.13 | 10.1.13org.apache.tomcat:tomcat:10.1.13 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 9.0.0-M1&&< 9.0.80 | 9.0.80org.apache.tomcat:tomcat:9.0.80 |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 8.5.0&&< 8.5.93 | 8.5.93org.apache.tomcat:tomcat:8.5.93 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 8.5.0&&< 8.5.93 | 8.5.93org.apache.tomcat.embed:tomcat-embed-core:8.5.93 |
| ☕Maven | org.apache.tomcat.embed:tomcat-embed-core | ≥ 9.0.0-M1&&< 9.0.80 | 9.0.80org.apache.tomcat.embed:tomcat-embed-core:9.0.80 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 11.0.0-M11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-41080 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-41080 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-41080. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The pki-servlet-engine package has been obsoleted by the Tomcat package. Therefore, this issue will be fixed in the Tomcat package rather than the pki-serlvet-engine package. Please follow the RHEL Tomcat trackers instead for the updates. Red Hat Satellite is not directly impacted by this issue, since it does not…
| Product | Fixed in | Advisory |
|---|---|---|
| JWS 6.0.1 | tomcat | RHSA-2024:1325 |
| Red Hat AMQ Broker 7 | tomcat | RHSA-2023:5946 |
| Red Hat AMQ Streams 2.6.0 | tomcat | RHSA-2023:7678 |
| Red Hat Enterprise Linux 8 | tomcat-1:9.0.62-27.el8_9.2 | RHSA-2024:0125 |
| Red Hat Enterprise Linux 9 | tomcat-1:9.0.62-37.el9_3.1 | RHSA-2024:0474 |
| Red Hat JBoss Web Server 5 | see advisory | RHSA-2023:7623 |
| Red Hat JBoss Web Server 5.7 on RHEL 7 | jws5-tomcat-0:9.0.62-19.redhat_00017.1.el7jws | RHSA-2023:7622 |
| Red Hat JBoss Web Server 6.0 on RHEL 8 | jws6-tomcat-0:10.1.8-6.redhat_00013.1.el8jws | RHSA-2024:1324 |
Frequently Asked Questions
Is CVE-2023-41080 in your dependencies?
O3 Security finds CVE-2023-41080 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.