Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-34151 – Unauthenticated Path Traversal / Arbitrary File Read – XWiki Platform < 17.10.5 and

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-34151 is a path traversal vulnerability (CWE-24) in XWiki Platform’s /skin/ action endpoint that allows an unauthenticated remote attacker to read arbitrary files accessible to the application server process. The flaw affects XWiki Platform deployments running on Jetty 12 or later and carries a CVSS v3.1/v4.0 base score of 8.2 (High). It is fixed in XWiki Platform 17.10.5 and 18.2.0.

Technical details

  • Root cause: the /skin/ action, handled by com.xpn.xwiki.web.SkinAction, resolves resource paths in a way that can be tricked into escaping the intended skin or web-application resource prefix when parent-directory segments are double-encoded.
  • Trigger condition: the issue only manifests when XWiki is deployed on Jetty 12 or later, because that version decodes the request path in a way that allows the double-encoded ../ sequences to survive traversal checks; Jetty versions before 12 and Tomcat do not appear affected.
  • Attack vector: unauthenticated, network-based — an attacker sends a crafted HTTP request to the /skin/ endpoint containing double-encoded parent-directory sequences (e.g., ..%252f).
  • Impact: arbitrary file read of resources accessible to the Jetty process, including internal configuration files such as WEB-INF/xwiki.cfg, and potentially host files outside the web application directory depending on deployment depth and operating system permissions. No integrity or availability impact is reported.
  • Fix approach: the vulnerable lookup was replaced with Environment.getResourceAsStream(String, String), which constrains resource resolution to the expected prefix.

Affected software

  • XWiki Platform versions prior to 17.10.5
  • XWiki Platform versions 18.0.0-rc-1 up to (but not including) 18.2.0
  • Only deployments running on Jetty 12 or later are exploitable via this issue

Severity

  • CVSS score: 8.2 (High)
  • CVSS v4.0 vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade XWiki Platform to version 17.10.5 or 18.2.0 (or later), which replace the vulnerable resource lookup.
  • If immediate patching is not possible: run XWiki on Jetty versions prior to 12, or on Apache Tomcat, since these are not reported as affected; additionally, monitor and restrict access to the /skin/ endpoint for requests containing encoded parent-directory traversal sequences as a temporary compensating control.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge