Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-72gw-fmmr-c4r4

HIGH

GHSA-72gw-fmmr-c4r4 is a high-severity (CVSS 7.5) vulnerability in github.com/hashicorp/vault. O3 Security confirms whether GHSA-72gw-fmmr-c4r4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization

Also known asBIT-vault-2026-4525CVE-2026-4525GO-2026-5199
Published
Apr 17, 2026
Updated
Jul 21, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/hashicorp/vault

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

If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/vault0.11.2No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Remediation status

    No patched version of github.com/hashicorp/vault has shipped for GHSA-72gw-fmmr-c4r4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-72gw-fmmr-c4r4 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-72gw-fmmr-c4r4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
O3 Security · Impact-Aware SCA

Is GHSA-72gw-fmmr-c4r4 in your dependencies?

O3 detects GHSA-72gw-fmmr-c4r4 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.