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

CVE-2014-7810 — tomcat

CVE-2014-7810 is a CWE-284 vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 13.3% (96th percentile). A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Improper Access Control in Apache Tomcat

Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 2, 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.
  • 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-2014-7810.

EPSS Exploitation Probability

via FIRST.org ↗
13.3%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk
8.17%10.5%12.8%15.2%9.5%13.3%May 26Sep 26Nov 26

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

Real-World Exposure

3 pkgs affected
☕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 Expression Language (EL) implementation in Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.58, and 8.x before 8.0.16 does not properly consider the possibility of an accessible interface implemented by an inaccessible class, which allows attackers to bypass a SecurityManager protection mechanism via a web application that leverages use of incorrect privileges during EL evaluation.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat≥ 6.0.0&&< 6.0.446.0.44org.apache.tomcat:tomcat:6.0.44
☕Mavenorg.apache.tomcat:tomcat≥ 7.0.0&&< 7.0.587.0.58org.apache.tomcat:tomcat:7.0.58
☕Mavenorg.apache.tomcat:tomcat≥ 8.0.0&&< 8.0.168.0.16org.apache.tomcat:tomcat:8.0.16

Affected Products

2 products · 239 configurations
Application
tomcatapache
103 versions
6.0.06.0.16.0.26.0.36.0.46.0.56.0.66.0.76.0.86.0.96.0.106.0.11
OS
debian linuxdebian
1 version
7.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 6.0.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-7810 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-94.el6_7RHSA-2016:0492
Red Hat Enterprise Linux 7tomcat-0:7.0.54-8.el7_2RHSA-2016:2046
Red Hat JBoss Enterprise Web Server 2 for RHEL 5tomcat6-0:6.0.41-15_patch_04.ep6.el5RHSA-2015:1622
Red Hat JBoss Web Server 2.1see advisoryRHSA-2015:1621

Frequently Asked Questions

The Expression Language (EL) implementation in Apache Tomcat 6.x before 6.0.44, 7.x before 7.0.58, and 8.x before 8.0.16 does not properly consider the possibility of an accessible interface implemented by an inaccessible class, which allows attackers to bypass a SecurityManager protection mechanism via a web application that leverages use of incorrect privileges during EL evaluation.
O3 Security · Impact-Aware SCA

Is CVE-2014-7810 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2014-7810: tomcat — Fixed in 6.0.44