EUVD-2026-107307
GHSA-fg56-q742-gmvf
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Undertow static file endpoint
-
ExploitRequest path resolving via symlink
-
ExecutionBypass prefix-only safe-directory check
-
ImpactRead files from sibling directory
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target run Undertow serving static files through PathResourceManager AND that the filesystem contain a symbolic link whose target path string-prefix-matches an authorized safe directory but actually points into a sibling directory (e.g. safe dir 'reports' and sibling 'reports-internal'). Limiting factors: the specific directory-naming collision and a usable symbolic link must already exist in the deployment, symlink-following must be in effect, and impact is confined to disclosure (read) of files in that sibling directory with no write or availability effect. These narrow preconditions are why attack complexity is high and impact is limited to low confidentiality. |
| Impact | Signals align on LOW real-world risk. The CVSS 3.1 base score of 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects a confidentiality-only information-disclosure flaw with high attack complexity and no integrity or availability impact. No EPSS score, KEV listing, or POC was provided in the input: per the precision rules this is 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. The AV:N vector asserts network reach, but the underlying weakness (CWE-22 prefix-only symlink validation in PathResourceManager) is only exploitable when a specific filesystem condition already exists - a sibling directory whose name shares the leading characters of an authorized safe directory, reachable via a symbolic link. This makes the 'network' exploitability contingent on local filesystem layout, consistent with the AC:H rating. Net assessment: not a priority for most defenders; it is a genuine but low-severity, high-precondition disclosure bug rather than a widely weaponizable vulnerability. No signals conflict, but note that the AV:N rating can overstate practical exploitability, which depends on deployment-specific directory naming and symlink presence. |
| Exploit ScenarioDerived | An attacker who can reach static content served by Undertow's PathResourceManager requests a path that resolves through a symbolic link whose target begins with the same characters as the configured safe base directory (for example safe base '/data/public' and sibling '/data/public-private'). Because the link target is validated by string prefix rather than full directory-name match, Undertow serves files from the sibling directory, disclosing their contents. No public exploit code was identified in the provided data, and the high attack complexity (AC:H) reflects the required directory-naming and symlink preconditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Path traversal in the Undertow web server's PathResourceManager, which serves static files from the filesystem, lets remote attackers read files outside the intended static-content root when a symbolic link resolves into a sibling directory whose name begins with the same characters as an authorized safe directory (for example 'reports' versus 'reports-internal'). The root cause is a string-prefix check that never verifies a full path-segment or directory boundary, so it fails to confirm the link's canonical target actually resides inside the approved directory. Affected deployments are those bundling Undertow's static resource handling, as reflected by Red Hat's CPEs for JBoss Enterprise Application Platform 7 and 8, Red Hat Fuse 7, Red Hat Build of Apache Camel for Spring Boot 4, Red Hat Single Sign-On 7, and RHEL 8/9 packages; the assessed severity is low (CVSS 3.1 base 3.7, AV:N/AC:H/PR:N/UI:N/C:L/I:N/A:N) because exploitation demands a pre-existing symlink plus a directory-name collision, and the outcome is limited to low-confidentiality file disclosure with no write or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the signals align on low real-world risk.
RemediationAI
No vendor-released patch version was identified in the available data for this CVE; track the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-114370 and Bugzilla issue https://bugzilla.redhat.com/show_bug.cgi?id=2528757 for the fixed Undertow build and the corresponding JBoss EAP, Fuse, Camel for Spring Boot, Single Sign-On, and RHEL 8/9 errata, and apply them as soon as they publish. In the interim, the most direct control is to disable symbolic-link following in the static content handler - constructing PathResourceManager with followLinks set to false (or the equivalent configuration in your embedded Undertow/Spring Boot setup) - at the cost of breaking any deployment that legitimately serves symlinked assets. Second, eliminate symbolic links from served content roots entirely, or restrict them to targets whose directory names share no prefix with the authorized root, so the collision condition ('reports' versus 'reports-internal') cannot arise; this requires an audit of the filesystem layout and may need renames plus configuration updates. Third, reduce exposure by running the server process under an account whose filesystem permissions deny read access to sibling directories adjacent to the static root, so a successful traversal yields no readable files - a permission tightening that can affect legitimate integrations. Finally, restrict network access to the static-serving endpoints to trusted clients where feasible, since the assessed vector is network-reachable and unauthenticated.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Undertow is the lightweight Java web server and servlet container embedded in Red Hat JBoss Enterprise Application Platform, WildFly, and numerous Red Hat middleware products (Fuse, Camel for Spring Boot, Single Sign-On), and it is also packaged for RHEL 8 and 9. Its PathResourceManager class backs static file serving: it maps a requested URL path onto a java.nio.file.Path under a configured base directory and decides whether a resolved resource is permissible. The vulnerability is a classic CWE-22 path traversal variant caused by an incomplete canonicalization check: when a symbolic link is encountered, the containment test compares the resolved target path against the protected directory using a plain string-prefix operation (startswith) instead of comparing normalized, canonical path segments or verifying that the parent directory equals the authorized root. Consequently a sibling directory such as '/srv/static/reports-internal' passes the check against the authorized '/srv/static/reports' because the string begins with the same characters. Exploitation therefore requires three converging conditions already present in the deployment: Undertow must be serving static content through PathResourceManager, symlink following must be enabled, and a usable symbolic link pointing into a similarly named sibling directory must exist on disk; an unauthenticated remote attacker (PR:N in the assessed vector) can then retrieve files from that sibling directory. The high attack complexity (AC:H) and low confidentiality-only impact (C:L, I:N, A:N) reflect these narrow environmental preconditions.
Know when Red Hat Enterprise Linux 8 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Reachable over the network without auth (AV:N/PR:N/UI:N) but contingent on a specific symlink and sibling-directory prefix collision (AC:H); disclosure-only, so C:L with I:N/A:N.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in the PathResourceManager component of the Undertow web server. This component is responsible for serving static files from the file system. The issue occurs because the mechanism used to verify if a symbolic link points to a safe location only checks if the target path starts with a specific string, without ensuring it matches a full directory name. This could allow an attacker to access files in a sibling directory if that directorys name starts with the same characters as an authorized safe directory.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Affected Products (CPE)CVE.org
More in Red Hat Enterprise Linux 8
View allHeap corruption via double-free in 389-ds-base's LDAP control parsing allows an unauthenticated remote attacker to crash
Remote code execution in Cockpit's web interface allows unauthenticated attackers to execute arbitrary commands on the h
Remote code execution in Samba's printing subsystem allows remote attackers to inject arbitrary shell commands via craft
Elevated-privilege container restoration in CRI-O 1.34 and later, including downstream Red Hat OpenShift Container Platf
Ghostscript can execute arbitrary shell commands with the privileges of its process when it renders a crafted PostScript
Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity
A signed integer overflow vulnerability exists in the libtiff library's putcontig8bitYCbCr44tile function that leads to
The system CA trust store shipped in Red Hat's ca-certificates RPM packages includes eMudhra root authorities that signe
Arbitrary code execution in GIMP's PSD import plugin allows an attacker to run code in the context of the user who opens
Authentication bypass in 389 Directory Server (shipped as Red Hat Directory Server 11-13 and within RHEL 6-10) lets remo
Remote code execution and privilege escalation in HPLIP (HP Linux Imaging and Printing) affects the hpcups print filter
Unauthenticated privilege escalation in FreeIPA (Red Hat Identity Management) allows a remote attacker to gain genuine a
Exploit-DB