Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2022-23181 — tomcat

HIGH

CVE-2022-23181 is a high-severity (CVSS 7) CWE-367 vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Local privilege escalation with FileStore

Also known asBIT-tomcat-2022-23181GHSA-9f3j-pm6f-9fm5
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.00%0.40%0.79%1.19%0.2%0.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-23181 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-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

The fix for bug CVE-2020-9484 introduced a time of check, time of use vulnerability into Apache Tomcat 10.1.0-M1 to 10.1.0-M8, 10.0.0-M5 to 10.0.14, 9.0.35 to 9.0.56 and 8.5.55 to 8.5.73 that allowed a local attacker to perform actions with the privileges of the user that the Tomcat process is using. This issue is only exploitable when Tomcat is configured to persist sessions using the FileStore.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 10.0.0&&< 10.0.1610.0.16org.apache.tomcat:tomcat:10.0.16
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.0&&< 9.0.589.0.58org.apache.tomcat:tomcat:9.0.58
☕Mavenorg.apache.tomcat:tomcatall versions8.5.75org.apache.tomcat:tomcat:8.5.75

Affected Products

7 products · 26 configurations
Application
tomcatapache
≥ 10.0.1 && ≤ 10.0.14
2 versions
10.0.010.1.0
OS
debian linuxdebian
2 versions
10.011.0
Application
agile engineering data managementoracle
1 version
6.2.1.0
Application
communications cloud native core policyoracle
1 version
1.15.0
Application
financial services crime and compliance management studiooracle
2 versions
8.0.8.2.08.0.8.3.0
Application
managed file transferoracle
2 versions
12.2.1.3.012.2.1.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update org.apache.tomcat:tomcat to 10.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23181 is resolved across your whole dependency graph.

  3. 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.

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.

Red HatModerate

In Red Hat Enterprise Linux 8, Red Hat Certificate System 10 and Identity Management are using the `pki-servlet-engine` component. This component embeds a version of Tomcat which is not affected by this flaw, as it does not include the fix for CVE-2020-9484. Additionally, in these specific contexts, the prerequisites…

ProductFixed inAdvisory
JWS 5.7.0tomcatRHSA-2022:7273
Red Hat Fuse 7.11tomcatRHSA-2022:5532
Red Hat JBoss Web Server 5.7 on RHEL 7jws5-tomcat-0:9.0.62-9.redhat_00005.1.el7jwsRHSA-2022:7272
Spring Boot 2.7.2.SP1tomcatRHSA-2023:0272

Frequently Asked Questions

The fix for bug CVE-2020-9484 introduced a time of check, time of use vulnerability into Apache Tomcat 10.1.0-M1 to 10.1.0-M8, 10.0.0-M5 to 10.0.14, 9.0.35 to 9.0.56 and 8.5.55 to 8.5.73 that allowed a local attacker to perform actions with the privileges of the user that the Tomcat process is using. This issue is only exploitable when Tomcat is configured to persist sessions using the FileStore.
O3 Security · Impact-Aware SCA

Is CVE-2022-23181 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2022-23181: tomcat — Fixed in 10.0.16