# CVE-2024-5798: Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims

> Attackers can bypass authentication in HashiCorp Vault by exploiting improper JWT audience validation, allowing unauthorized access to protected resources.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jun 2024
- **Updated:** 4 Nov 2025
- **Also known as:** BIT-vault-2024-5798, GHSA-32cj-5wx4-gq8p, GO-2024-2921

## What is CVE-2024-5798?

CVE-2024-5798 is a low-severity authentication bypass vulnerability in Hashicorp Vault, published on 12 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vault and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected.

This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-5798?

8 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | From 0.11.0 | 1.16.3, 1.17.0 |
| `github.com/hashicorp/vault` | Go | From 0.11.0 | 1.15.9 |
| `github.com/hashicorp/vault` | Go | From 0.11.0 | 1.15.9 |
| `github.com/hashicorp/vault` | Go | From 1.16.0-rc1 | 1.16.3 |
| `github.com/hashicorp/vault` | Go | From 1.16.0-rc1 | 1.16.3 |
| `github.com/hashicorp/vault` | Go | From 1.17.0-rc1 | 1.17.0 |
| `github.com/hashicorp/vault` | Go | From 1.17.0-rc1 | 1.17.0 |
| `vault` | Bitnami | From 0.11.0 | 1.16.2 |

Products: Hashicorp Vault.

## How do I fix CVE-2024-5798?

Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.16.3, 1.17.0 or 1.15.9.

## Is CVE-2024-5798 being exploited?

There is no known exploitation of CVE-2024-5798 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5798 and fix it if it is affected.

What it is: CVE-2024-5798 is a low-severity authentication bypass vulnerability in Hashicorp Vault, published on 12 Jun 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-5798 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected from 0.11.0; fixed in 1.16.3, 1.17.0
- github.com/hashicorp/vault (Go): affected from 0.11.0; fixed in 1.15.9
- github.com/hashicorp/vault (Go): affected from 0.11.0; fixed in 1.15.9
- github.com/hashicorp/vault (Go): affected from 1.16.0-rc1; fixed in 1.16.3
- github.com/hashicorp/vault (Go): affected from 1.16.0-rc1; fixed in 1.16.3
- github.com/hashicorp/vault (Go): affected from 1.17.0-rc1; fixed in 1.17.0
- github.com/hashicorp/vault (Go): affected from 1.17.0-rc1; fixed in 1.17.0
- vault (Bitnami): affected from 0.11.0; fixed in 1.16.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5798/ (Markdown: https://insights.sbomify.com/CVE-2024-5798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5798
- OSV: https://osv.dev/vulnerability/CVE-2024-5798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5798/
Summaries are generated and may contain mistakes; the official description above is the record.