Skip to content
Fencer Vulns
low 2.6

CVE-2024-5798 json

Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims

published 2024-06-12 2 y ago modified 2026-09-08 2 mo ago also BIT-vault-2024-5798 , EUVD-2024-1892 , GHSA-32cj-5wx4-gq8p , GO-2024-2921

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/hashicorp/vault 1.15.9, 1.16.3, 1.17.0
  • bitnami vault 1.16.2
  • HashiCorp Vault 1.14.13, 1.15.9, 1.16.2
  • HashiCorp Vault Enterprise 1.14.13, 1.15.9, 1.16.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-5798 updated cvss 2.6

github.com/hashicorp/vault: HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims in github.com/hashicorp/vault

  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/odf-rhel8-operator, odf4/ocs-must-gather-rhel8, odf4/ocs-metrics-exporter-rhel9, odf4/odf-multicluster-rhel9-operator
    affected: no fix available
  • Red Hat Trusted Application Pipeline cli-v02
    affected: no fix available “Fix deferred”
  • Red Hat Openshift Data Foundation 4 odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator, odf4/ocs-rhel9-operator
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
GitHub 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=1.17.0-rc1, <1.17.0
>=1.16.0-rc1, <1.16.3
>=0.11.0, <1.15.9
>=0.11.0, <1.16.3
1.17.0
1.16.3
1.15.9
bitnami vault
>=0.11.0, <1.16.2
1.16.2

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.