Atomicorp WAF Research Note: CVE-2025-41242

Spring Framework - Path Traversal

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2025-41242
• Name: Spring Framework - Path Traversal
• Severity: Medium
• CVSS: 5.9 (v3.1) (Medium)
• CVSS version: 3.1
• CVSS source: vmware CNA
• CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Attack vector: Network
  • Attack complexity: High
  • Privileges required: None
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality impact: High
  • Integrity impact: None
  • Availability impact: None
• CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
• Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-126 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
• Vendor: VMware
• Vulnerable product: Spring Framework
• CVE published: 2025-08-18
• CVE last modified: 2026-06-17
• EPSS: 0.0205; 80.2th percentile (FIRST (opens in a new tab) )
• Latest Update: 2026-07-03
• Selected Rule IDs observed: 347009
• Matching rules: 1; rules with blocking actions: 1
• Would-block Rule IDs: 347009
• Request surfaces inspected: Request URI

Vulnerability Description

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 (opens in a new tab)
• the application serves static resources https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title (opens in a new tab)  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.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (347009 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: VMware Spring Framework versions earlier than 6.2.10.
   • Affected versions: VMware Spring Framework versions earlier than 6.1.22.
   • Affected versions: VMware Spring Framework versions earlier than 5.3.44.
   • No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• CVE authority reference: http://spring.io/security/cve-2025-41242 (opens in a new tab)

Test or Research Source

• Source: http/cves/2025/CVE-2025-41242.yaml (opens in a new tab)
• Tags: cve, cve2025, jetty, lfi, spring, uri

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .