How severe is GHSA-5mp4-32rr-v3x5?

GHSA-5mp4-32rr-v3x5 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5mp4-32rr-v3x5?

GHSA-5mp4-32rr-v3x5 affects the following packages: io.digdag:digdag-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5mp4-32rr-v3x5?

Update io.digdag:digdag-server to 0.10.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5mp4-32rr-v3x5 is resolved across your whole dependency graph.

How do I detect GHSA-5mp4-32rr-v3x5 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.digdag:digdag-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5mp4-32rr-v3x5 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 GHSA-5mp4-32rr-v3x5?

O3 pinpoints whether GHSA-5mp4-32rr-v3x5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5mp4-32rr-v3x5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5mp4-32rr-v3x5 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 GHSA-5mp4-32rr-v3x5?

GHSA-5mp4-32rr-v3x5 has an EPSS (Exploit Prediction Scoring System) score of 29.6%, 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 GHSA-5mp4-32rr-v3x5?

GHSA-5mp4-32rr-v3x5 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.

When was GHSA-5mp4-32rr-v3x5 published, and has it been updated?

GHSA-5mp4-32rr-v3x5 was published on February 14, 2024 and was last updated on October 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-5mp4-32rr-v3x5: Absolute path traversal vulnerability in d…

EPSS Exploitation Probability

via FIRST.org ↗

29.6%probability of exploitation in next 30 days

Moderate Risk98th percentile+22.30%

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.

Blast Radius

1 pkg affected

☕io.digdag:digdag-server

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

Summary

Treasure Data's digdag workload automation system is susceptible to a path traversal vulnerability if it's configured to store log files locally.

Impact

This issue may lead to Information Disclosure.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.digdag:digdag-server`	all versions	0.10.5.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.digdag:digdag-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.digdag:digdag-server to 0.10.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5mp4-32rr-v3x5 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 pinpoints whether GHSA-5mp4-32rr-v3x5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5mp4-32rr-v3x5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Treasure Data's digdag workload automation system is susceptible to a path traversal vulnerability if it's configured to store log files locally. ### Impact This issue may lead to Information Disclosure.

O3 Security · Impact-Aware SCA

Is GHSA-5mp4-32rr-v3x5 in your dependencies?

O3 detects GHSA-5mp4-32rr-v3x5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-5mp4-32rr-v3x5