The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78 for the EncryptInterceptor incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was not correct. While the EncryptInterceptor does provide confidentiality and integrity protection, it does not protect against all risks associated with running over any untrusted network, particularly DoS risks.
CVE-2022-29885
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.7 because EPSS predicted 73% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
- 105 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- High exploitation likelihood — EPSS 73%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
105 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2022-29885, in our KEV-Exposure radar’s Shodan-derived sample.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 7.5
- EG Score
- 8.7HIGHhigh confidence
- EG Risk
- 78EG Risk 78/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation73% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 73%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 73% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 12, 2022
Last Modified
October 8, 2026
Advisory Details (5)
Auto-updated Oct 8, 2026Packet Storm
http://packetstormsecurity.com/files/171728/Apache-Tomcat-10.1-Denial-Of-Service.html[SECURITY] [DSA 5265-1] tomcat9 security update
https://www.debian.org/security/2022/dsa-5265[SECURITY] [DLA 3160-1] tomcat9 security update
https://lists.debian.org/debian-lts-announce/2022/10/msg00029.htmlPatch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | tomcat8-user (8.0.32-1ubuntu1.13+esm1) @ xenial | 2026-10-21 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(6 across 6 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat9 | 9.0.16-4 ... 9.0.31-1~deb10u6 (12 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat9 | 9.0.43-1, 9.0.43-2~deb11u1, 9.0.43-2~deb11u2, 9.0.43-2~deb11u3 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat9 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat9 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| tomcat9 | — |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.apache.tomcat:tomcat | 8.5.38 ... 8.5.78 (35 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 6× in last 7d / 24× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 86 of 137 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 14 repeat rows among the latest 100 are merged into the row they repeat. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-21 07:27 UTCEG score recompute
- 2026-10-21 07:27 UTCVendor advisory
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-18 08:36 UTCEG score recompute
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-12 18:55 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-11 23:20 UTCEG score recompute
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-08 22:25 UTCVendor advisory
- 2026-10-08 21:30 UTCEG score recompute
- 2026-10-08 21:30 UTCVendor advisory
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-30 15:54 UTCEG score recompute
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-24 22:16 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
Show 61 moreShow fewer
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-05 14:25 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-23 00:16 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-19 00:59 UTCOSV refresh
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-03 20:27 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-23 02:10 UTCEG score recompute▲ 1.20
- 2026-07-22 22:57 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-19 02:27 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-18 10:02 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-17 11:59 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-15 16:56 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-13 06:11 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-11 08:25 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-06 16:25 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-07-05 02:28 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-07-01 15:04 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-06-29 10:32 UTCOSV refresh
- 2026-06-28 14:06 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-06-28 04:54 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-06-25 13:48 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-06-24 14:03 UTCEPSS rescoreEPSS 72% · 99th percentile
- 2026-06-23 21:31 UTCEPSS rescoreEPSS 72% · 99th percentile
Publicly available exploits
(3 references)Public exploit code is referenced for this CVE (1 Exploit-DB entry, 2 GitHub PoCs). Defenders should treat patch urgency accordingly.
- Exploit-DBEDB-51262Published Apr 5, 2023
Apache Tomcat 10.1 - Denial Of Service
Open source ↗ - GitHub PoCiveresk/CVE-2022-29885Published Jul 1, 2022
Apache Tomcat DoS (CVE-2022-29885) Exploit
Open source ↗ - GitHub PoCquynhlab/CVE-2022-29885Published Jun 30, 2022
Apache Tomcat CVE-2022-29885
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:10:tomcat9
- CVE-2020-13935NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2020-13934NVD 7.5EG 8.4EPSS p99HIGH
- CVE-2021-33037NVD 5.3EG 8.3EPSS p100HIGH
- CVE-2021-41079EG 7.5EPSS p94HIGH
- CVE-2020-11996EG 7.5EPSS p98HIGH
- CVE-2022-23181EG 7.0HIGH
- CVE-2021-30640EG 6.5EPSS p96MEDIUM
- CVE-2023-41080EG 6.1EPSS p94MEDIUM
- CVE-2023-45648EG 5.3EPSS p93MEDIUM
- CVE-2023-42795EG 5.3MEDIUM
Same vendor
4 shownubuntu:USN-6943-1
Frequently asked(5)
What is CVE-2022-29885?
When was the CVE record for CVE-2022-29885 published?
Is CVE-2022-29885 actively exploited?
What is the CVSS score of CVE-2022-29885?
How do I remediate CVE-2022-29885?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-29885
Is Your Infrastructure Affected by CVE-2022-29885?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.