Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims

CVSS 3.1 2.6 LOWEUVD CVSS 3.1 2.6 CVSS 3.1 · [email protected] · Secondary 2.6 LOWCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating LOWFixed by github.com/hashicorp/vault 1.17.0Fixed by github.com/hashicorp/vault 1.16.3Fixed by github.com/hashicorp/vault 1.15.9osv · severity unknownFixed by github.com/hashicorp/vault 1.16.3Fixed by github.com/hashicorp/vault 1.17.0KEV status unknown

cve-program · CVE-2024-5798

Published

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

Read the publisher's advisory

euvd · EUVD-2024-1892

Published

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

Read the publisher's advisory

nvd · CVE-2024-5798

Published

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

Read the publisher's advisory

osv · GHSA-32cj-5wx4-gq8p

Published

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

Read the publisher's advisory

osv · GO-2024-2921

Published

HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims in github.com/hashicorp/vault. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/hashicorp/vault before v1.15.9.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

17 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

22 Nov 2026 14:26:33 UTC

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, …

euvd · EUVD-2024-1892 · Published

20 Nov 2026 14:12:02 UTC

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, …

euvd · EUVD-2024-1892 · Published

17 Nov 2026 03:32:50 UTC

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, …

euvd · EUVD-2024-1892 · Published

15 Nov 2026 02:38:49 UTC

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, …

euvd · EUVD-2024-1892 · Published

13 Nov 2026 02:26:55 UTC

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, …

euvd · EUVD-2024-1892 · Published

11 Nov 2026 01:39:04 UTC

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, …

euvd · EUVD-2024-1892 · Published

9 Nov 2026 01:12:19 UTC

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, …

euvd · EUVD-2024-1892 · Published

7 Nov 2026 00:37:25 UTC

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, …

euvd · EUVD-2024-1892 · Published

5 Nov 2026 00:04:25 UTC

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, …

euvd · EUVD-2024-1892 · Published

2 Nov 2026 23:05:47 UTC

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, …

euvd · EUVD-2024-1892 · Published

31 Oct 2026 22:13:52 UTC

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, …

euvd · EUVD-2024-1892 · Published

29 Oct 2026 21:24:09 UTC

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, …

euvd · EUVD-2024-1892 · Published

27 Oct 2026 20:57:10 UTC

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, …

euvd · EUVD-2024-1892 · Published

25 Oct 2026 01:17:17 UTC

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, …

nvd · CVE-2024-5798 · Published

24 Oct 2026 13:19:41 UTC

HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims

osv · GHSA-32cj-5wx4-gq8p · Published

24 Oct 2026 13:19:41 UTC

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

osv · GO-2024-2921 · Published

23 Oct 2026 15:48:27 UTC

Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims

cve-program · CVE-2024-5798 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 16:32 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current