How severe is CVE-2024-5798?

CVE-2024-5798 has a CVSS 3.x base score of 2.6, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2024-5798 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-5798?

CVE-2024-5798 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2024-5798?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-5798 have an EU (EUVD) identifier?

Yes. CVE-2024-5798 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1892.

When was CVE-2024-5798 published?

CVE-2024-5798 was published on 2024-06-12 and last updated on 2026-06-17.

CVE-2024-5798

CVE-2024-5798 is a low-severity vulnerability in Hashicorp Vault with a CVSS 3.x base score of 2.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-287.

Key facts

Severity: Low (CVSS 3.x base score 2.6)
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-1892
Weakness: CWE-287
Affected product: Hashicorp Vault
Published: 2024-06-12
Last modified: 2026-06-17

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

Frequently asked questions

What is CVE-2024-5798?: 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
How severe is CVE-2024-5798?: CVE-2024-5798 has a CVSS 3.x base score of 2.6, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2024-5798 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-5798?: CVE-2024-5798 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-5798?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-5798 have an EU (EUVD) identifier?: Yes. CVE-2024-5798 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-1892.
When was CVE-2024-5798 published?: CVE-2024-5798 was published on 2024-06-12 and last updated on 2026-06-17.

References

https://discuss.hashicorp.com/t/hcsec-2024-11-vault-incorrectly-validated-json-web-tokens-jwt-audience-claims/67770

Affected products (2)

cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Hashicorp Vault

CVE-2020-35192 — Critical (CVSS 9.8): The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker…
CVE-2020-12757 — Critical (CVSS 9.8): HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly…
CVE-2025-6000 — Critical (CVSS 9.1): A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution…
CVE-2022-40186 — Critical (CVSS 9.1): An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine…
CVE-2022-36129 — Critical (CVSS 9.1): HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an…
CVE-2020-10661 — Critical (CVSS 9.1): HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing…

All CVEs affecting Hashicorp Vault →

Other CWE-287 (Improper Authentication) vulnerabilities

CVE-2026-20317 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Secure Workload engineering…
CVE-2026-19977 — Critical (CVSS 10.0): A vulnerability was detected in EFM ipTIME A3004T 14.19.0. The affected element is the function…
CVE-2026-59500 — Critical (CVSS 10.0): CWE-287: Improper Authentication
CVE-2024-27253 — Critical (CVSS 10.0): IBM DOORS Next 7.0.3 through 7.0.3 Interim Fix 018 could allow an authenticated user to bypass security logic to…
CVE-2026-56162 — Critical (CVSS 10.0): Improper authentication in Azure SQL Database allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-62825 — Critical (CVSS 10.0): Improper authentication in Azure Key Vault allows an unauthorized attacker to elevate privileges over a network.

Browse all CWE-287 (Improper Authentication) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE:

167.172.59.75 (ipv4-addr)