Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Apache Tomcat vulnerable to SecurityManager bypass

CVE-2016-6796GHSA-3mjp-p938-4329

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.tomcat:tomcat 9.0.0.M10, 8.5.5, 8.0.37, 7.0.71, 6.0.46), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.apache.tomcat:tomcat

    Affected
    >= 9.0.0.M1, <= 9.0.0.M9>= 8.5.0, <= 8.5.4>= 8.0.0.RC1, <= 8.0.36>= 7.0.0, <= 7.0.70>= 6.0.0, <= 6.0.45
    Fixed in
    8.5.5, 8.0.37, 9.0.0.M10, 6.0.46, 7.0.71

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2016-6796: 8.32% estimated exploitation activity in the next 30 days; percentile 94.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A malicious web application running on Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 was able to bypass a configured SecurityManager via manipulation of the configuration parameters for the JSP Servlet.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-3mjp-p938-4329

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-6796

Advisory: Apache Tomcat vulnerable to SecurityManager bypass
IDs: CVE-2016-6796, GHSA-3mjp-p938-4329
Record: https://patchnext.com/advisories/cve-2016-6796 (revision 1, source checked 26 Oct 2026, 16:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.tomcat:tomcat 9.0.0.M10, 8.5.5, 8.0.37, 7.0.71, 6.0.46. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat:tomcat: affected >= 9.0.0.M1, <= 9.0.0.M9; >= 8.5.0, <= 8.5.4; >= 8.0.0.RC1, <= 8.0.36; >= 7.0.0, <= 7.0.70; >= 6.0.0, <= 6.0.45; fixed in 8.5.5, 8.0.37, 9.0.0.M10, 6.0.46, 7.0.71

## Suggested inspection (read-only)
- Maven org.apache.tomcat:tomcat: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.tomcat:tomcat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3mjp-p938-4329 (GitHub-reviewed advisory GHSA-3mjp-p938-4329 lists affected ranges: Maven org.apache.tomcat:tomcat >=9.0.0.M1 =8.5.0 =8.0.0.RC1 =7.0.0 =6.0.0 <=6.0.45)

Commands are suggestions: review each one before running it.

Loading voting…