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 and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when…

CVSS 3.1 · [email protected] · Secondary 2.6 LOWCVSS 3.1 · [email protected] · Primary 7.5 HIGHCheck source for fixed versionsKEV status unknown

Historical advisory recorded 25 Oct 2026 01:17:17 UTC. Read the latest 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

Affected versions, risk and source history

nvd · CVE-2024-5798

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-287

Original publisher date fields

published: 2024-06-12T19:15:51.413

lastModified: 2026-06-17T08:16:40.123

2 source CPE criteria · context only
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

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