What is GHSA-6XV5-86Q9-7XR8?

GHSA-6XV5-86Q9-7XR8 is a medium-severity security vulnerability in github.com/cyphar/filepath-securejoin (go), affecting versions < 0.2.4. It is fixed in 0.2.4.

Which versions of github.com/cyphar/filepath-securejoin are affected by GHSA-6XV5-86Q9-7XR8?

github.com/cyphar/filepath-securejoin (go) versions < 0.2.4 is affected.

Is there a fix for GHSA-6XV5-86Q9-7XR8?

Yes. GHSA-6XV5-86Q9-7XR8 is fixed in 0.2.4. Upgrade to this version or later.

Is GHSA-6XV5-86Q9-7XR8 exploitable, and should I be worried?

Whether GHSA-6XV5-86Q9-7XR8 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 GHSA-6XV5-86Q9-7XR8 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 GHSA-6XV5-86Q9-7XR8?

Upgrade github.com/cyphar/filepath-securejoin to 0.2.4 or later.

GHSA-6XV5-86Q9-7XR8

Q: Which versions of github.com/cyphar/filepath-securejoin are affected by GHSA-6XV5-86Q9-7XR8?

github.com/cyphar/filepath-securejoin (go) versions < 0.2.4 is affected.

Q: Is there a fix for GHSA-6XV5-86Q9-7XR8?

Yes. GHSA-6XV5-86Q9-7XR8 is fixed in 0.2.4. Upgrade to this version or later.

Q: Is GHSA-6XV5-86Q9-7XR8 exploitable, and should I be worried?

Whether GHSA-6XV5-86Q9-7XR8 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.

Q: What actually determines whether GHSA-6XV5-86Q9-7XR8 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.

Q: How do I fix GHSA-6XV5-86Q9-7XR8?

Upgrade github.com/cyphar/filepath-securejoin to 0.2.4 or later.

Summary

SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced

Workarounds

Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin.

References

See #9.

Impact

For Windows users of github.com/cyphar/filepath-securejoin, until v0.2.4 it was possible for certain rootfs and path combinations (in particular, where a malicious Unix-style /-separated unsafe path was used with a Windows-style rootfs path) to result in generated paths that were outside of the provided rootfs.

It is unclear to what extent this has a practical impact on real users, but given the possible severity of the issue we have released an emergency patch release that resolves this issue.

Thanks to @pjbgf for discovering, debugging, and fixing this issue (as well as writing some tests for it).

Affected versions

github.com/cyphar/filepath-securejoin (< 0.2.4)

Security releases

github.com/cyphar/filepath-securejoin → 0.2.4 (go)

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

c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.

Frequently Asked Questions

What is GHSA-6XV5-86Q9-7XR8? GHSA-6XV5-86Q9-7XR8 is a medium-severity security vulnerability in github.com/cyphar/filepath-securejoin (go), affecting versions < 0.2.4. It is fixed in 0.2.4.
Which versions of github.com/cyphar/filepath-securejoin are affected by GHSA-6XV5-86Q9-7XR8? github.com/cyphar/filepath-securejoin (go) versions < 0.2.4 is affected.
Is there a fix for GHSA-6XV5-86Q9-7XR8? Yes. GHSA-6XV5-86Q9-7XR8 is fixed in 0.2.4. Upgrade to this version or later.
Is GHSA-6XV5-86Q9-7XR8 exploitable, and should I be worried? Whether GHSA-6XV5-86Q9-7XR8 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 GHSA-6XV5-86Q9-7XR8 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 GHSA-6XV5-86Q9-7XR8? Upgrade github.com/cyphar/filepath-securejoin to 0.2.4 or later.