How severe is GHSA-42wg-hm62-jcwg?

No CVSS score has been assigned to GHSA-42wg-hm62-jcwg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-42wg-hm62-jcwg?

GHSA-42wg-hm62-jcwg affects the following packages: org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat.embed:tomcat-embed-core (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat-catalina (Maven), org.apache.tomcat:tomcat-catalina (Maven), and 1 more. Ecosystems affected: Maven.

How do I fix GHSA-42wg-hm62-jcwg?

Update org.apache.tomcat.embed:tomcat-embed-core to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42wg-hm62-jcwg is resolved across your whole dependency graph.

How do I detect GHSA-42wg-hm62-jcwg in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat.embed:tomcat-embed-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-42wg-hm62-jcwg 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 GHSA-42wg-hm62-jcwg actively exploited in the wild?

No public exploit code has been indexed for GHSA-42wg-hm62-jcwg 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 GHSA-42wg-hm62-jcwg?

GHSA-42wg-hm62-jcwg has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th 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 GHSA-42wg-hm62-jcwg?

GHSA-42wg-hm62-jcwg is classified as CWE-426 (CWE-426). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-42wg-hm62-jcwg published, and has it been updated?

GHSA-42wg-hm62-jcwg was published on June 16, 2025 and was last updated on October 29, 2025. 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

Apache Tomcat installer for Windows has an untrusted search path vulnerabilityGHSA-42wg-hm62-jcwg

Fix: apache/tomcat@28726cc

GHSA-42wg-hm62-jcwg is a CWE-426 vulnerability in org.apache.tomcat.embed:tomcat-embed-core. A fix is available for org.apache.tomcat.embed:tomcat-embed-core — see the affected versions and patch details below.

Also known asBIT-tomcat-2025-49124CVE-2025-49124

Published

Jun 16, 2025

Updated

Oct 29, 2025

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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 GHSA-42wg-hm62-jcwg.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

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

Real-World Exposure

9 pkgs affected

☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat.embed:tomcat-embed-core☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat-catalina☕org.apache.tomcat:tomcat-catalina+1 more

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

Untrusted Search Path vulnerability in Apache Tomcat installer for Windows. During installation, the Tomcat installer for Windows used icacls.exe without specifying a full path.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0 through 10.1.41, from 9.0.23 through 9.0.105. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 through 8.5.100 and 7.0.95 through 7.0.109. Other EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, which fix the issue.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 11.0.0-M1&&< 11.0.8	11.0.8`org.apache.tomcat.embed:tomcat-embed-core:11.0.8`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 10.1.0&&< 10.1.42	10.1.42`org.apache.tomcat.embed:tomcat-embed-core:10.1.42`
☕Maven	`org.apache.tomcat.embed:tomcat-embed-core`	≥ 9.0.23&&< 9.0.106	9.0.106`org.apache.tomcat.embed:tomcat-embed-core:9.0.106`
☕Maven	`org.apache.tomcat:tomcat`	≥ 11.0.0-M1&&< 11.0.8	11.0.8`org.apache.tomcat:tomcat:11.0.8`
☕Maven	`org.apache.tomcat:tomcat`	≥ 10.1.0&&< 10.1.42	10.1.42`org.apache.tomcat:tomcat:10.1.42`
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.23&&< 9.0.106	9.0.106`org.apache.tomcat:tomcat:9.0.106`

Affected Products

1 product · 3 configurations

Application

tomcatapache

≥ 11.0.0 && < 11.0.8

range

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.embed:tomcat-embed-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat.embed:tomcat-embed-core to 11.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42wg-hm62-jcwg 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.

Frequently Asked Questions

Untrusted Search Path vulnerability in Apache Tomcat installer for Windows. During installation, the Tomcat installer for Windows used icacls.exe without specifying a full path. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0 through 10.1.41, from 9.0.23 through 9.0.105. Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, which fix the issue.

O3 Security · Impact-Aware SCA

Is GHSA-42wg-hm62-jcwg in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works