CVE Intelligence
High Denial of service

CVE-2022-29885 — EncryptInterceptor does not provide complete protection on insecure networks

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.

Published May 12, 2022 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: apache

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Public exploit/PoC (exploitdb)+8
  • EPSS 73.5% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
73.47%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Apache Software Foundation
Tomcat and 2 more
CVSS base
7.5
High · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — lists.apache.org (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Tomcat, Debian Debian Linux, Oracle Hospitality Cruise Shipboard Property Management System).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Tomcat version 10.1.0-milestone2version 10.1.0-milestone9version 10.1.0-milestone8version 10.1.0-milestone7version 10.1.0-milestone6version 10.1.0-milestone5version 10.1.0-milestone4version 10.1.0-milestone3
and 9 more version 10.1.0-milestone14version 10.1.0-milestone13version 10.1.0-milestone12version 10.1.0-milestone11version 10.1.0-milestone10version 10.1.0-milestone1≥ 10.0.0 and ≤ 10.0.20≥ 9.0.13 and ≤ 9.0.62≥ 8.5.38 and ≤ 8.5.78
Vulnerable NIST National Vulnerability Database
Apache Software Foundation Tomcat version Apache Tomcat 9 9.0.13 to 9.0.62version Apache Tomcat 10 10.0.0-M1 to 10.0.20version Apache Tomcat 10.1 10.1.0-M1 to 10.1.0-M14version Apache Tomcat 8.5 8.5.38 to 8.5.78 Vulnerable CVE Program (cve.org) e CISA ADP
Debian Debian Linux version 11.0version 10.0 Vulnerable NIST National Vulnerability Database
Oracle Hospitality Cruise Shipboard Property Management System version 20.2.1 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-400 · Uncontrolled Resource Consumption

Other CVEs with this weakness →

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 73.47%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · apache software foundation/apache tomcat
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2022
  • CVE published
    May 12, 2022 · apache

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

6 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
CWE-400
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-73180 Insufficient Session Expiration vulnerability in Apache Tomcat meant that if the session… Aug 25, 2026
  • Critical CVE-2026-65905 Authentication Bypass by Capture-replay in Apache Software Foundation Tomcat Aug 25, 2026
  • High CVE-2026-68763 Uncontrolled Resource Consumption in Apache Software Foundation Tomcat Aug 25, 2026
  • High CVE-2026-65927 Off-by-one Error vulnerability in Apache Tomcat impacting the [N] flag on the rewrite… Aug 25, 2026
  • High CVE-2026-66422 Improper Authorization in Apache Software Foundation Tomcat Aug 25, 2026
  • Critical CVE-2026-68525 Incorrect Authorization in Apache Software Foundation Tomcat Aug 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-29885 is "EncryptInterceptor does not provide complete protection on insecure networks", rated High. It affects Tomcat (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 73.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.