Skip to content

CVE-2025-41242

Path Traversal: Is CVE-2025-41242 real, exploitable, or a false positive? Here's the community verdict.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
5.9 Medium
CVSS
Exploitation prob.
2%
FIRST EPSS
Weakness
CWE-22 · Path Traversal
CWE

Moderate signals. Triage by your actual exposure and reachability.

public exploits

links to sources — we don’t host code

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

scanner noise

anonymous, aggregated from real reports · via Denoizr
ScannerFlagged inTurned out noise
Mend2 scans0%

How often this CVE was flagged by each scanner and how much turned out to be noise (false positives), aggregated anonymously from de-noised reports. Higher noise means the alert is more often not a real risk — verify your exposure.

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Spring Framework MVC applications can be vulnerable to a “Path Traversal Vulnerability” when deployed on a non-compliant Servlet container. An application can be vulnerable when all the following are true: * the application is deployed as a WAR or with an embedded Servlet container * the Servlet container does not reject suspicious sequences https://jakarta.ee/specifications/servlet/6.1/jakarta-servlet-spec-6.1.html#uri-path-canonicalization * the application serves static resources https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with Spring resource handling We have verified that applications deployed on Apache Tomcat or Eclipse Jetty are not vulnerable, as long as default security features are not disabled in the configuration. Because we cannot check exploits against all Servlet containers and configuration variants, we strongly recommend upgrading your application.

Published

Embed this verdict
TruePositive verdict for CVE-2025-41242
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2025-41242/badge.svg)](https://www.truepositive.app/cve/CVE-2025-41242)
HTML
<a href="https://www.truepositive.app/cve/CVE-2025-41242"><img src="https://www.truepositive.app/cve/CVE-2025-41242/badge.svg" alt="TruePositive verdict for CVE-2025-41242"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    No confirmed in-the-wild exploitation or public exploit was found for this yet.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-22 · Path Traversal.