GHSA-fp52-qw33-mfmw
HIGHGHSA-fp52-qw33-mfmw is a high-severity (CVSS 8.2) CWE-290 vulnerability in github.com/hashicorp/vault. O3 Security confirms whether GHSA-fp52-qw33-mfmw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault
Real-World Exposure
github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vaultReal-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
HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hashicorp/vault | ≥ 0.8.1&&< 1.2.5 | 1.2.5 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.3.0&&< 1.3.8 | 1.3.8 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.4.0&&< 1.4.4 | 1.4.4 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.5.0&&< 1.5.1 | 1.5.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/vault. 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/hashicorp/vault to 1.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fp52-qw33-mfmw 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-fp52-qw33-mfmw 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-fp52-qw33-mfmw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Frequently Asked Questions
Is GHSA-fp52-qw33-mfmw in your dependencies?
O3 detects GHSA-fp52-qw33-mfmw across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.