Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-hq8m-v68g-8cf8

Opencast has a partial path traversal vulnerability in UI config

CVSS 2.7 LowEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 29 Aug 2025, 15:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.opencastproject:opencast-user-interface-configurationMaven<17.7 || >=18.0, <18.117.7, 18.1
Identifiers
GHSA-hq8m-v68g-8cf8 · CVE-2025-55202
Weakness (CWE)
CWE-23
Tags
Published
29 Aug 2025
Updated
29 Aug 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Opencast's UI configuration module (org.opencastproject:opencast-user-interface-configuration) is affected in versions before 17.7 and from 18.0 up to but not including 18.1. A path traversal check does not account for the file separator, so an attacker may be able to read files in a sibling folder whose name starts with the UI config directory name, such as ui-config-hidden next to ui-config, if Opencast can read them. Upgrade to version 17.7 or 18.1. As a mitigation, check whether any folders share the ui-config name prefix.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.7 Low 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.