GHSA-6xv5-86q9-7xr8
SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced
GHSA-6xv5-86q9-7xr8 is a vulnerability with no CVSS score yet in github.com/cyphar/filepath-securejoin, published September 7, 2023. No source lists public exploit code. Fixed in github.com/cyphar/filepath-securejoin 0.2.4.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.2.4github.com/cyphar/filepath-securejoin
Description
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).
Patches
c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.
Workarounds
Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin.
References
See #9.
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/cyphar/filepath-securejoinGo | before 0.2.4 | 0.2.4 |
What each source reports
GitHub AdvisoriesNo score
SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced
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).
Patches
c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.
Workarounds
Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin.
References
See #9.
- Record
GHSA-6xv5-86q9-7xr8- Updated
- 2026-11-02
OSVNo score
SecureJoin: on windows, paths outside of the rootfs could be inadvertently produced
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).
Patches
c121231e1276e11049547bee5ce68d5a2cfe2d9b is the patch fixing this issue. v0.2.4 contains the fix.
Workarounds
Users could use filepath.FromSlash() on all unsafe paths before passing them to filepath-securejoin.
References
See #9.
- Record
GHSA-6xv5-86q9-7xr8- Updated
- 2026-11-02
OSVGO-2023-2048No score
Paths outside of the rootfs could be produced on Windows in github.com/cyphar/filepath-securejoin
Certain rootfs and path combinations result in generated paths that are outside of the provided rootfs on Windows.
- Record
GO-2023-2048- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
References
github.com/cyphar/filepath-securejoin/security/advisories/GHSA-6xv5-86q9-7xr8