How severe is CVE-2026-59084?

CVE-2026-59084 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-59084?

Affected package information for CVE-2026-59084 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-59084?

No fixed release is recorded for CVE-2026-59084 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-59084 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-59084 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-59084 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-59084 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-59084?

CVE-2026-59084 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-59084?

CVE-2026-59084 is classified as CWE-1059 (CWE-1059). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-59084 published, and has it been updated?

CVE-2026-59084 was published on July 14, 2026 and was last updated on September 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

CRITICAL severity

CVE-2026-59084 — tomcat

CRITICAL

CVE-2026-59084 is a critical-severity (CVSS 9.1) CWE-1059 vulnerability. No vendor fix is recorded yet; mitigation options are listed below.

Apache Tomcat: EncryptInterceptor requirements not clearly documented

Also known asBIT-tomcat-2026-59084

Published

Jul 14, 2026

Updated

Sep 19, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-2026-59084.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Description

Insufficient Technical Documentation vulnerability in Apache Tomcat since the requirements to securely configure the EncryptInterceptor were not clearly documented.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.23, from 10.1.0-M1 through 10.1.56, from 9.0.13 through 9.0.119, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Other versions that have reached end of support may also be affected.

Users are recommended to upgrade to version 11.0.24, 10.1.57 or 9.0.120 which fix the issue.

Affected Products

1 product · 5 configurations

Application

tomcatapache

≥ 11.0.0 && ≤ 11.0.23

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-59084 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
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 HatLow

This Low impact vulnerability in Apache Tomcat arises from insufficient documentation for the EncryptInterceptor. Without clear guidance on secure configuration, administrators might inadvertently deploy the interceptor in a way that weakens security, rather than a direct code flaw. This issue affects Red Hat products…

Workaround published by Red Hat

To mitigate this issue, ensure that the EncryptInterceptor in Apache Tomcat is configured according to secure best practices. Review existing configurations of EncryptInterceptor to verify that all security requirements are met and that no insecure settings are in place. If the EncryptInterceptor is not actively used, no specific action is required.

Source: Red Hat security advisory for CVE-2026-59084 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`tomcat9-1:9.0.120-1.el10_2`	RHSA-2026:68651
Red Hat Enterprise Linux 10.0 Extended Update Support	`tomcat9-1:9.0.120-1.el10_0`	RHSA-2026:67163
Red Hat Enterprise Linux 8	`tomcat-1:9.0.120-1.el8_10`	RHSA-2026:68677
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`tomcat-1:9.0.120-1.el8_8`	RHSA-2026:68680
Red Hat Enterprise Linux 9	`tomcat-1:9.0.120-2.el9_8`	RHSA-2026:68660
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions	`tomcat-1:9.0.120-1.el9_2`	RHSA-2026:68678
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions	`tomcat-1:9.0.120-1.el9_4`	RHSA-2026:68679
Red Hat Enterprise Linux 9.6 Extended Update Support	`tomcat-1:9.0.120-1.el9_6`	RHSA-2026:68659

Frequently Asked Questions

Insufficient Technical Documentation vulnerability in Apache Tomcat since the requirements to securely configure the EncryptInterceptor were not clearly documented. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.23, from 10.1.0-M1 through 10.1.56, from 9.0.13 through 9.0.119, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.24, 10.1.57 or 9.0.120 which fix the issue.

O3 Security · Impact-Aware SCA

Is CVE-2026-59084 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works