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. 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-p93v-m2r2-4387 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-p93v-m2r2-4387?

O3 pinpoints whether GHSA-p93v-m2r2-4387 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-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 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

GHSA-p93v-m2r2-4387

Fix: google/fscrypt@91aa3eb

GHSA-p93v-m2r2-4387 is a CWE-255 vulnerability in github.com/google/fscrypt. O3 Security confirms whether GHSA-p93v-m2r2-4387 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of service via insufficient metadata validation

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 Jun 8, 2026 · OSV.dev, NVD, 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

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. 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 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
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-p93v-m2r2-4387 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-p93v-m2r2-4387. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-p93v-m2r2-4387 across Go 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