NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2016-5388 — tomcat-catalina

HIGHFix: apache/tomcat@1b91e91

CVE-2016-5388 is a high-severity (CVSS 8.1) CWE-284 vulnerability in org.apache.tomcat:tomcat-catalina. EPSS puts its 30-day exploitation probability at 50.9% (99th percentile). A fix is available for org.apache.tomcat:tomcat-catalina — see the affected versions and patch details below.

Improper Access Control in Apache Tomcat

Also known asGHSA-v646-rx6w-r3qq
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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-2016-5388.

EPSS Exploitation Probability

via FIRST.org ↗
50.9%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
32.5%40.1%47.6%55.1%36.8%50.9%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina

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

Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue. NOTE: the vendor states "A mitigation is planned for future releases of Tomcat, tracked as CVE-2016-5388"; in other words, this is not a CVE ID for a vulnerability.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 7.0.0&&< 7.0.727.0.72org.apache.tomcat:tomcat-catalina:7.0.72
☕Mavenorg.apache.tomcat:tomcat-catalina≥ 8.0.0&&< 8.5.58.5.5org.apache.tomcat:tomcat-catalina:8.5.5

Affected Products

11 products · 18 configurations
Application
tomcatapache
≥ 8.0 && ≤ 8.5.4
range
Application
system management homepagehp
≤ 7.5.5.0
range
OS
linuxoracle
2 versions
67
OS
enterprise linux desktopredhat
2 versions
6.07.0
OS
enterprise linux hpc noderedhat
2 versions
6.07.0
OS
enterprise linux hpc node eusredhat
1 version
7.2

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-catalina, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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
ProductFixed inAdvisory
Red Hat Enterprise Linux 6tomcat6-0:6.0.24-98.el6_8RHSA-2016:2045
Red Hat Enterprise Linux 7tomcat-0:7.0.54-8.el7_2RHSA-2016:2046
Red Hat JBoss Web Server 3.0see advisoryRHSA-2016:1624
Red Hat JBoss Web Server 3 for RHEL 6httpd24-0:2.4.6-62.ep7.el6RHSA-2016:1636
Red Hat JBoss Web Server 3 for RHEL 7httpd24-0:2.4.6-62.ep7.el7RHSA-2016:1635

Frequently Asked Questions

Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue. NOTE: the vendor states "A mitigation is planned for future releases of Tomcat, tracked as CVE-2016-5388"; in other words, this is not a CVE ID for a vulnerability.
O3 Security · Impact-Aware SCA

Is CVE-2016-5388 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2016-5388: tomcat-catalina — Fixed in 7.0.72