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

Improper Access Control in Apache TomcatGHSA-mv42-px54-87jw

HIGHFix: apache/tomcat@50f1b1d

GHSA-mv42-px54-87jw is a high-severity (CVSS 8.8) CWE-264 vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 13.1% (96th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Also known asCVE-2016-0714
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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 GHSA-mv42-px54-87jw.

EPSS Exploitation Probability

via FIRST.org ↗
13.1%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
5.26%8.52%11.8%15.0%13.2%13.1%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

4 pkgs affected
☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

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

The session-persistence implementation in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 mishandles session attributes, which allows remote authenticated users to bypass intended SecurityManager restrictions and execute arbitrary code in a privileged context via a web application that places a crafted object in a session.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 9.0.0.M1&&< 9.0.0.M29.0.0.M2org.apache.tomcat:tomcat:9.0.0.M2
☕Mavenorg.apache.tomcat:tomcat≥ 8.0.0.RC1&&< 8.0.328.0.32org.apache.tomcat:tomcat:8.0.32
☕Mavenorg.apache.tomcat:tomcat≥ 7.0.0&&< 7.0.707.0.70org.apache.tomcat:tomcat:7.0.70
☕Mavenorg.apache.tomcat:tomcat≥ 6.0.0&&< 6.0.466.0.46org.apache.tomcat:tomcat:6.0.46

Affected Products

3 products · 104 configurations
Application
tomcatapache
90 versions
6.0.06.0.16.0.26.0.46.0.106.0.116.0.136.0.146.0.166.0.186.0.206.0.24
OS
ubuntu linuxcanonical
4 versions
12.0414.0415.1016.04
OS
debian linuxdebian
2 versions
7.08.0

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

  2. Fix

    Update org.apache.tomcat:tomcat to 9.0.0.M2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mv42-px54-87jw is resolved across your whole dependency graph.

  3. Workarounds

    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 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.69-10.el7RHSA-2016:2599
Red Hat JBoss Enterprise Web Server 2 for RHEL 6tomcat7-0:7.0.54-23_patch_05.ep6.el6RHSA-2016:2807
Red Hat JBoss Web Server 2.1tomcat7RHSA-2016:2808
Red Hat JBoss Web Server 3.0see advisoryRHSA-2016:1089
Red Hat JBoss Web Server 3 for RHEL 6httpd24-0:2.4.6-61.ep7.el6RHSA-2016:1087
Red Hat JBoss Web Server 3 for RHEL 7httpd24-0:2.4.6-61.ep7.el7RHSA-2016:1088

Frequently Asked Questions

The session-persistence implementation in Apache Tomcat 6.x before 6.0.45, 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 mishandles session attributes, which allows remote authenticated users to bypass intended SecurityManager restrictions and execute arbitrary code in a privileged context via a web application that places a crafted object in a session.
O3 Security · Impact-Aware SCA

Is GHSA-mv42-px54-87jw in your dependencies?

Find it across Maven, including transitive dependencies.

Improper Access Control in Apache Tomcat (High 8.8)