# CVE-2024-9180: GO-2024-3191 - Vault Community Edition privilege escalation vulnerability in github.com/hashicorp/vault

Source: https://junglewise.ai/threats/cve-2024-9180-vault-community-edition-privilege-escalation-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-10-11  
License: CC BY 4.0 with a link back

CVE-2024-9180 · Severity: low · CVSS 3.1 · Published 2024-10-11

Vault Community Edition privilege escalation vulnerability in github.com/hashicorp/vault

Technologies: [github.com/hashicorp/vault (Go)](https://junglewise.ai/threats/technologies/github-com-hashicorp-vault), [github.com/openbao/openbao (Go)](https://junglewise.ai/threats/technologies/github-com-openbao-openbao). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2024-9180 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-9180 being exploited in the wild.

**How severe is CVE-2024-9180?** Low severity, with a CVSS score of 3.1, published 11 October 2024.

**Which products and versions are affected?** github.com/hashicorp/vault (Go) SEMVER:introduced=0,fixed=1.18.0; github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=2.0.3.

**Is there a fix for CVE-2024-9180?** Yes. github.com/hashicorp/vault (Go): upgrade to 1.18.0 or later; github.com/openbao/openbao (Go): upgrade to 2.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-9180?** Check whether you run github.com/hashicorp/vault (Go) or github.com/openbao/openbao (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/hashicorp/vault (Go): upgrade to 1.18.0 or later

  ```sh
  go get github.com/hashicorp/vault@v1.18.0
  ```

- github.com/openbao/openbao (Go): upgrade to 2.0.3 or later

  ```sh
  go get github.com/openbao/openbao@v2.0.3
  ```


## Affected products

- github.com/hashicorp/vault (Go) SEMVER:introduced=0,fixed=1.18.0
- github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=2.0.3

## Identifiers

- CVE-2024-9180
- GHSA-rr8j-7w34-xp5j
- GO-2024-3191

## Related threats

- [OpenBao Agent information disclosure via stdout in exec rendering mode](https://junglewise.ai/threats/cve-2026-77285-openbao-agent-information-disclosure-via-stdout-in-exec-rendering)
- [OpenBao recovery mode timing attack token leakage](https://junglewise.ai/threats/cve-2026-63132-openbao-recovery-mode-timing-attack-token-leakage)
- [OpenBao authorization bypass in policy enforcement for LIST operations](https://junglewise.ai/threats/cve-2026-63131-openbao-authorization-bypass-in-policy-enforcement-for-list)
- [OpenBao templated policies privilege escalation via wildcard characters](https://junglewise.ai/threats/cve-2026-71543-openbao-templated-policies-privilege-escalation-via-wildcard)
- [OpenBao denial of service via Transit engine key creation](https://junglewise.ai/threats/cve-2026-55776-openbao-denial-of-service-via-transit-engine-key-creation)