Is there a fix for CVE-2025-55202?

Yes. CVE-2025-55202 is fixed in 17.7, 18.1. Upgrade to this version or later.

Is CVE-2025-55202 exploitable, and should I be worried?

Whether CVE-2025-55202 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-55202 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-55202

Q: What is CVE-2025-55202?

CVE-2025-55202 is a low-severity security vulnerability in org.opencastproject:opencast-user-interface-configuration (maven), affecting versions < 17.7. It is fixed in 17.7, 18.1.

Q: Which versions of org.opencastproject:opencast-user-interface-configuration are affected by CVE-2025-55202?

org.opencastproject:opencast-user-interface-configuration (maven) versions < 17.7 is affected.

Q: How do I fix CVE-2025-55202?

Upgrade: org.opencastproject:opencast-user-interface-configuration to 17.7 or later, org.opencastproject:opencast-user-interface-configuration to 18.1 or later.

Summary

Opencast has a partial path traversal vulnerability in UI config

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

Impact

Affected versions

org.opencastproject:opencast-user-interface-configuration (< 17.7) org.opencastproject:opencast-user-interface-configuration (= 18.0)

Security releases

org.opencastproject:opencast-user-interface-configuration → 17.7 (maven) org.opencastproject:opencast-user-interface-configuration → 18.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.opencastproject:opencast-user-interface-configuration to 17.7 or later; org.opencastproject:opencast-user-interface-configuration to 18.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-55202? CVE-2025-55202 is a low-severity security vulnerability in org.opencastproject:opencast-user-interface-configuration (maven), affecting versions < 17.7. It is fixed in 17.7, 18.1.
Which versions of org.opencastproject:opencast-user-interface-configuration are affected by CVE-2025-55202? org.opencastproject:opencast-user-interface-configuration (maven) versions < 17.7 is affected.
Is there a fix for CVE-2025-55202? Yes. CVE-2025-55202 is fixed in 17.7, 18.1. Upgrade to this version or later.
Is CVE-2025-55202 exploitable, and should I be worried? Whether CVE-2025-55202 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-55202 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-55202?
- Upgrade org.opencastproject:opencast-user-interface-configuration to 17.7 or later
- Upgrade org.opencastproject:opencast-user-interface-configuration to 18.1 or later