How severe is CVE-2015-5351?

CVE-2015-5351 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-5351?

CVE-2015-5351 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-5351?

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

How do I detect CVE-2015-5351 in my Maven dependencies?

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.

How do I mitigate CVE-2015-5351 if there is no patch (or I can't update yet)?

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.

Is CVE-2015-5351 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-5351 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-5351?

CVE-2015-5351 has an EPSS (Exploit Prediction Scoring System) score of 9.7%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-5351?

CVE-2015-5351 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-5351 published, and has it been updated?

CVE-2015-5351 was published on May 14, 2022 and was last updated on February 18, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2015-5351 — tomcat

HIGH

CVE-2015-5351 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Apache Tomcat allows remote attackers to bypass a CSRF protection mechanism by using a token

Published

May 14, 2022

Updated

Feb 18, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 1, 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-2015-5351.

EPSS Exploitation Probability

via FIRST.org ↗

9.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

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 (1) Manager and (2) Host Manager applications in Apache Tomcat 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M2 establish sessions and send CSRF tokens for arbitrary new requests, which allows remote attackers to bypass a CSRF protection mechanism by using a token.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	7.0.68`org.apache.tomcat:tomcat:7.0.68`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0&&< 8.0.31	8.0.31`org.apache.tomcat:tomcat:8.0.31`
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M0&&< 9.0.0.M2	9.0.0.M2`org.apache.tomcat:tomcat:9.0.0.M2`

Affected Products

3 products · 74 configurations

Application

tomcatapache

65 versions

7.0.07.0.27.0.47.0.57.0.67.0.107.0.117.0.127.0.147.0.167.0.197.0.20

ubuntu linuxcanonical

4 versions

12.0414.0415.1016.04

debian linuxdebian

2 versions

7.08.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update org.apache.tomcat:tomcat to 7.0.68 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5351 is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`tomcat-0:7.0.69-10.el7`	RHSA-2016:2599
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`tomcat7-0:7.0.54-23_patch_05.ep6.el6`	RHSA-2016:2807
Red Hat JBoss Web Server 2.1	`tomcat7`	RHSA-2016:2808
Red Hat JBoss Web Server 3.0	see advisory	RHSA-2016:1089
Red Hat JBoss Web Server 3 for RHEL 6	`httpd24-0:2.4.6-61.ep7.el6`	RHSA-2016:1087
Red Hat JBoss Web Server 3 for RHEL 7	`httpd24-0:2.4.6-61.ep7.el7`	RHSA-2016:1088

UbuntuHIGH

USN-3024-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-5351 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works