Is github.com/google/fscrypt 0.2 vulnerable?
Go · 10 releases from 0.2.0 to 0.2.9 · latest github.com/google/fscrypt is 0.3.7 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. github.com/google/fscrypt 0.2.9, the last 0.2 release, is affected by 8 known security advisories (6 medium, 2 low), including CVE-2022-25327, CVE-2022-25326, CVE-2022-25327. 2 more affect earlier 0.2.x releases. Upgrade to 0.3.3 or later to fix all of them.
go get github.com/google/fscrypt@v0.3.3Is your project on an affected github.com/google/fscrypt?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/google/fscrypt 0.2.9
Possible filesystem space exhaustion by local users in github.com/google/fscrypt
- Affected
- <0.3.3
- Fixed in
- 0.3.3
User login denial of service in github.com/google/fscrypt
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Denial of service via insufficient metadata validation
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Possible privilege escalation via bash completion script
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Possible filesystem space exhaustion by local users
- Affected
- <0.3.3
- Fixed in
- 0.3.3
User login denial of service in github.com/google/fscrypt
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Uncontrolled Resource Consumption in github.com/google/fscrypt
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Command injection in github.com/google/fscrypt
- Affected
- <0.3.3
- Fixed in
- 0.3.3
Fixed within 0.2.x, affecting earlier releases
Privilege Escalation in fscrypt
- Affected
- <0.2.4
- Fixed in
- 0.2.4
Privilege escalation in github.com/google/fscrypt
- Affected
- <0.2.4
- Fixed in
- 0.2.4
Every github.com/google/fscrypt 0.2.x release
Affected: 0.2.0 to 0.2.9. Latest github.com/google/fscrypt: 0.3.7.
| Version | Known advisories |
|---|---|
| github.com/google/fscrypt 0.2.9 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.8 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.7 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.6 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.5 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.4 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328 |
| github.com/google/fscrypt 0.2.3 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328, CVE-2018-6558, CVE-2018-6558 |
| github.com/google/fscrypt 0.2.2 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328, CVE-2018-6558, CVE-2018-6558 |
| github.com/google/fscrypt 0.2.1 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328, CVE-2018-6558, CVE-2018-6558 |
| github.com/google/fscrypt 0.2.0 | CVE-2022-25326, CVE-2022-25327, CVE-2022-25327, GHSA-w4f8-fxq2-j35v, CVE-2022-25326, CVE-2022-25327, CVE-2022-25326, CVE-2022-25328, CVE-2018-6558, CVE-2018-6558 |
Which of your client projects are still on github.com/google/fscrypt 0.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/google/fscrypt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/google/fscrypt versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.