VDB

CVE-2025-41242

CVE-2025-41242 PUBLISHED CVSS 5.9 MEDIUM

CVE-2025-41242: Path traversal vulnerability on non-compliant Servlet containers

Reported by vmware · Published August 18, 2025

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
apache-activemq-fips-6.1Chainguard6.1.8-r7

Risk scores

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

Affected products

VendorProductVersions
VMwareSpring Framework6.2.x, 6.1.x, 5.3.x
chainguardapache-activemq-fips-6.10
chainguardapache-nifi-registry0
Mavenorg.springframework:spring-webmvc6.0.0, 5.3.0, 6.2.0
chainguardconductor-fips0
chainguardconductor0
chainguardapache-activemq-6.10
wolfiapache-nifi-registry0
VMwareSpring Framework5.3.x, 6.2.x, 6.1.x
chainguardthingsboard0
wolfithingsboard0

Timeline

  • Aug 13, 2025 CVE Published
  • Aug 18, 2025 EPSS Score (30 in total, the first dated here)
  • Aug 18, 2025 Coalition ESS Score (8 in total, the first dated here)
  • Mar 17, 2026 Security Advisory
  • Mar 23, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-41242
vulnetix vdb fixes CVE-2025-41242

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-41242/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›