How severe is CVE-2025-55202?

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

Which packages are affected by CVE-2025-55202?

CVE-2025-55202 affects the following packages: org.opencastproject:opencast-user-interface-configuration (Maven), org.opencastproject:opencast-user-interface-configuration (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-55202?

Update org.opencastproject:opencast-user-interface-configuration to 17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55202 is resolved across your whole dependency graph.

How do I detect CVE-2025-55202 in my Maven dependencies?

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

How do I mitigate CVE-2025-55202 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2025-55202 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-55202 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 CVE-2025-55202?

CVE-2025-55202 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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 CVE-2025-55202?

CVE-2025-55202 is classified as CWE-23 (CWE-23). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-55202 published, and has it been updated?

CVE-2025-55202 was published on August 29, 2025 and was last updated on October 28, 2026. 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-2025-55202 — opencast-user-interface-c…

Fix: opencast/opencast@e2cc65d

CVE-2025-55202 is a CWE-23 vulnerability in org.opencastproject:opencast-user-interface-configuration. A fix is available for org.opencastproject:opencast-user-interface-configuration — see the affected versions and patch details below.

Opencast has a partial path traversal vulnerability in UI config

Also known asGHSA-hq8m-v68g-8cf8

Published

Aug 29, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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 CVE-2025-55202.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.opencastproject:opencast-user-interface-configuration☕org.opencastproject:opencast-user-interface-configuration

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

The protections against path traversal attacks in the UI config module are insufficient, still partially allowing for attacks in very specific cases.

The path is checked without checking for the file separator. This could allow attackers access to files within another folder which starts with the same path. For example, the default UI config directory is placed at /etc/opencast/ui-config. Without this patch, an attacker can get access to files in a folder /etc/opencast/ui-config-hidden if those files are readable by Opencast.

General path traversal is not possible. For example, an attacker cannot exploit this to access files in /etc/opencast/encoding or even in /etc/opencast/ directly.

How dangerous is this?

Theoretically, this vulnerability may be exploited to get access to some non-public files. However, given the default structure of Opencast's configuration, this is extremely unlikely to hit any users. There can be but one ui-config folders. This makes it quite unlikely for any user to have created an additional folder starting with ui-config. Users could also rename this folder, but since there is no real reason for anyone to do this, this, again is extremely unlikely to trigger this issue.

How to fix the issue

To mitigate this, check if you have folders which start with the same path as your ui-config folder
A fix is available in https://github.com/opencast/opencast/pull/6979
Updating to Opencast 17.7 or 18.1 will fix the issue

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:opencast-user-interface-configuration`	all versions	17.7`org.opencastproject:opencast-user-interface-configuration:17.7`
☕Maven	`org.opencastproject:opencast-user-interface-configuration`	≥ 18.0&&< 18.1	18.1`org.opencastproject:opencast-user-interface-configuration:18.1`

Affected Products

1 product · 2 configurations

Application

opencastapereo

< 17.7

1 version

18.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-user-interface-configuration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencastproject:opencast-user-interface-configuration to 17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55202 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

The protections against path traversal attacks in the UI config module are insufficient, still partially allowing for attacks in very specific cases. The path is checked without checking for the file separator. This could allow attackers access to files within another folder which starts with the same path. For example, the default UI config directory is placed at `/etc/opencast/ui-config`. Without this patch, an attacker can get access to files in a folder `/etc/opencast/ui-config-hidden` if those files are readable by Opencast. General path traversal is not possible. For example, an attack

O3 Security · Impact-Aware SCA

Is CVE-2025-55202 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works