How severe is GHSA-mr4h-qf9j-f665?

GHSA-mr4h-qf9j-f665 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mr4h-qf9j-f665?

GHSA-mr4h-qf9j-f665 affects the following packages: github.com/hashicorp/vault (Go). Ecosystems affected: Go.

How do I fix GHSA-mr4h-qf9j-f665?

Update github.com/hashicorp/vault to 1.20.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mr4h-qf9j-f665 is resolved across your whole dependency graph.

How do I detect GHSA-mr4h-qf9j-f665 in my Go dependencies?

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.

How do I mitigate GHSA-mr4h-qf9j-f665 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-mr4h-qf9j-f665?

O3 pinpoints whether GHSA-mr4h-qf9j-f665 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-mr4h-qf9j-f665 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mr4h-qf9j-f665 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-mr4h-qf9j-f665?

GHSA-mr4h-qf9j-f665 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mr4h-qf9j-f665 published, and has it been updated?

GHSA-mr4h-qf9j-f665 was published on August 1, 2025 and was last updated on February 4, 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

CRITICAL severity

GHSA-mr4h-qf9j-f665

CRITICAL

GHSA-mr4h-qf9j-f665 is a critical-severity (CVSS 9.1) Code Injection vulnerability in github.com/hashicorp/vault. O3 Security confirms whether GHSA-mr4h-qf9j-f665 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration

Also known asBIT-vault-2025-6000CVE-2025-6000GO-2025-3838

Published

Aug 1, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

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

A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a plugin directory is set in Vault’s configuration. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hashicorp/vault`	≥ 0.8.0&&< 1.20.1	1.20.1

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/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.20.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mr4h-qf9j-f665 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-mr4h-qf9j-f665 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-mr4h-qf9j-f665. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mr4h-qf9j-f665 in your dependencies?

O3 detects GHSA-mr4h-qf9j-f665 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