How severe is GHSA-w4f8-fxq2-j35v?

No CVSS score has been assigned to GHSA-w4f8-fxq2-j35v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w4f8-fxq2-j35v?

GHSA-w4f8-fxq2-j35v affects the following packages: github.com/google/fscrypt (Go). Ecosystems affected: Go.

How do I fix GHSA-w4f8-fxq2-j35v?

Update github.com/google/fscrypt to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4f8-fxq2-j35v is resolved across your whole dependency graph.

How do I detect GHSA-w4f8-fxq2-j35v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/fscrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w4f8-fxq2-j35v if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-w4f8-fxq2-j35v actively exploited in the wild?

No public exploit code has been indexed for GHSA-w4f8-fxq2-j35v 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.

When was GHSA-w4f8-fxq2-j35v published, and has it been updated?

GHSA-w4f8-fxq2-j35v was published on March 1, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Possible privilege escalation via bash completion scriptGHSA-w4f8-fxq2-j35v

GHSA-w4f8-fxq2-j35v is a security vulnerability in github.com/google/fscrypt. A fix is available for github.com/google/fscrypt — see the affected versions and patch details below.

Published

Mar 1, 2022

Updated

Mar 1, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 1, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/google/fscrypt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The bash completion script for fscrypt through v0.3.2 allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the fscrypt bash completion script to complete mountpoint paths. We recommend upgrading to v0.3.3 or above.

For more details, see CVE-2022-25328.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/google/fscrypt`	all versions	0.3.3`go get github.com/google/fscrypt@v0.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/fscrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/google/fscrypt to 0.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4f8-fxq2-j35v is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

The bash completion script for `fscrypt` through v0.3.2 allows injection of commands via crafted mountpoint paths, allowing privilege escalation under a specific set of circumstances. A local user who has control over mountpoint paths could potentially escalate their privileges if they create a malicious mountpoint path and if the system administrator happens to be using the `fscrypt` bash completion script to complete mountpoint paths. We recommend upgrading to v0.3.3 or above. For more details, see [CVE-2022-25328](https://www.cve.org/CVERecord?id=CVE-2022-25328).

O3 Security · Impact-Aware SCA

Is GHSA-w4f8-fxq2-j35v in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works