CVE-2026-59083
Apache Tomcat ≤ 8.0.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-59083 is a critical-severity Hex Encoding (CWE-177) vulnerability in Apache Tomcat. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-43638
Vulnerability Data
Improper Handling of URL Encoding (Hex Encoding) vulnerability in Apache Tomcat's rewrite valve allowed security constraint bypass for some configurations. 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.0.M1 through 9.0.119, from 8.5.0 through…
more
8.5.100. 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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Direct security constraint bypass in public-facing Tomcat rewrite valve enables exploitation of the web application (T1190).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces the security constraints that the URL-encoding flaw in the rewrite valve is bypassing.
Requires validation and canonicalization of URL inputs to block hex-encoding bypasses before constraint evaluation.
Boundary-protection mechanisms (e.g., WAF rules) can inspect and drop malformed or encoded requests targeting the rewrite valve.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct URL-encoding/decoding and input validation during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches URL-decoding flaws before release, but does not itself define coding rules.
Secure SDLC processes include validation steps that reduce CWE-177, yet the control is broader than this single weakness.
Application security requirements explicitly call for input validation and canonicalization, directly preventing improper URL decoding.
Secure coding standards mandate proper handling and decoding of encoded inputs, eliminating CWE-177.