How severe is GHSA-p93v-m2r2-4387?

No CVSS score has been assigned to GHSA-p93v-m2r2-4387 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p93v-m2r2-4387?

GHSA-p93v-m2r2-4387 affects the following packages: github.com/google/fscrypt (Go). Ecosystems affected: Go.

How do I fix GHSA-p93v-m2r2-4387?

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-p93v-m2r2-4387 is resolved across your whole dependency graph.

How do I detect GHSA-p93v-m2r2-4387 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-p93v-m2r2-4387 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-p93v-m2r2-4387 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p93v-m2r2-4387 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-p93v-m2r2-4387?

GHSA-p93v-m2r2-4387 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 1th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p93v-m2r2-4387?

GHSA-p93v-m2r2-4387 is classified as CWE-255 (CWE-255), Incorrect Default Permissions (CWE-276). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p93v-m2r2-4387 published, and has it been updated?

GHSA-p93v-m2r2-4387 was published on March 1, 2022 and was last updated on June 8, 2026. 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

Denial of service via insufficient metadata validationGHSA-p93v-m2r2-4387

Fix: google/fscrypt@91aa3eb

GHSA-p93v-m2r2-4387 is a CWE-255 vulnerability in github.com/google/fscrypt. A fix is available for github.com/google/fscrypt — see the affected versions and patch details below.

Also known asCVE-2022-25327 GHSA-8vwm-8vj8-rqjfGO-2022-0340

Published

Mar 1, 2022

Updated

Jun 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p93v-m2r2-4387.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs1th percentile — riskier than 1% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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 PAM module for fscrypt through v0.3.2 doesn't adequately validate fscrypt metadata files, allowing users to create malicious metadata files that prevent other users from logging in. A local user can cause a denial of service by creating a fscrypt metadata file that prevents other users from logging into the system. We recommend upgrading to v0.3.3 or above.

For more details, see CVE-2022-25327.

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`

Affected Products

1 product · 1 configurations

Application

fscryptgoogle

< 0.3.3

range

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-p93v-m2r2-4387 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 PAM module for `fscrypt` through v0.3.2 doesn't adequately validate `fscrypt` metadata files, allowing users to create malicious metadata files that prevent other users from logging in. A local user can cause a denial of service by creating a `fscrypt` metadata file that prevents other users from logging into the system. We recommend upgrading to v0.3.3 or above. For more details, see [CVE-2022-25327](https://www.cve.org/CVERecord?id=CVE-2022-25327).

O3 Security · Impact-Aware SCA

Is GHSA-p93v-m2r2-4387 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works