How severe is CVE-2014-7816?

No CVSS score has been assigned to CVE-2014-7816 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-7816?

CVE-2014-7816 affects the following packages: io.undertow:undertow-core (Maven), io.undertow:undertow-core (Maven), io.undertow:undertow-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-7816?

Update io.undertow:undertow-core to 1.0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-7816 is resolved across your whole dependency graph.

How do I detect CVE-2014-7816 in my Maven dependencies?

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

How do I mitigate CVE-2014-7816 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.

How does O3 Security protect against CVE-2014-7816?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-7816 can be triaged on real exposure rather than presence alone.

Is CVE-2014-7816 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-7816, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-7816?

CVE-2014-7816 has an EPSS (Exploit Prediction Scoring System) score of 25.1%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2014-7816?

CVE-2014-7816 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2014-7816?

A Metasploit module references CVE-2014-7816, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2014-7816 published, and has it been updated?

CVE-2014-7816 was published on May 17, 2022 and was last updated on December 7, 2024. 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

CVE-2014-7816 — undertow-core

CVE-2014-7816 is a Path Traversal vulnerability in io.undertow:undertow-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for io.undertow:undertow-core — see the affected versions and patch details below.

Improper Limitation of a Pathname to a Restricted Directory in JBoss Undertow

Published

May 17, 2022

Updated

Dec 7, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

25.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕io.undertow:undertow-core☕io.undertow:undertow-core☕io.undertow:undertow-core

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

Directory traversal vulnerability in JBoss Undertow 1.0.x before 1.0.17, 1.1.x before 1.1.0.CR5, and 1.2.x before 1.2.0.Beta3, when running on Windows, allows remote attackers to read arbitrary files via a .. (dot dot) in a resource URI.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.undertow:undertow-core`	≥ 1.0.0&&< 1.0.17	1.0.17`io.undertow:undertow-core:1.0.17`
☕Maven	`io.undertow:undertow-core`	≥ 1.1.0.Beta1&&< 1.1.0.CR5	1.1.0.CR5`io.undertow:undertow-core:1.1.0.CR5`
☕Maven	`io.undertow:undertow-core`	≥ 1.2.0.Beta1&&< 1.2.0.Beta3	1.2.0.Beta3`io.undertow:undertow-core:1.2.0.Beta3`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Directory traversal vulnerability in JBoss Undertow 1.0.x before 1.0.17,…

github.comMetasploitOct 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.undertow:undertow-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.undertow:undertow-core to 1.0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-7816 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-7816 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-7816. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-7816 in your dependencies?

O3 Security finds CVE-2014-7816 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works