NVD / CVE Program· CNA HashiCorp

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

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: HashiCorp Vault 1.14.13, 1.15.9, 1.16.2; HashiCorp Vault Enterprise 1.14.13, 1.15.9, 1.16.2.
Severity is disputed: the assigning authority (CNA) scores it 2.6, NVD 7.5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to HashiCorp Vault 1.14.13, 1.15.9, 1.16.2; HashiCorp Vault Enterprise 1.14.13, 1.15.9, 1.16.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jun 12, 2024
Updated: Jun 17, 2026
EPSS: 0.3% · 27th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · HashiCorp: 2.6; 4.9 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
hashicorp	vault	cpe:2.3:a:hashicorp:vault

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

hashicorp vault0.11.0 and later · before 1.15.9
hashicorp vault1.16.0 and later · before 1.16.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.

HashiCorp Vault
- 0.11.0 and later · before 1.16.2affected · semverfixed in 1.15.9, 1.14.13
HashiCorp Vault Enterprise
- 0.11.0 and later · before 1.16.2affected · semverfixed in 1.15.9, 1.14.13

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/hashicorp/vault	from 0.11.0 · before 1.15.9	1.15.9
Go	github.com/hashicorp/vault	from 0.11.0 · before 1.16.3	1.16.3
Go	github.com/hashicorp/vault	from 1.16.0-rc1 · before 1.16.3	1.16.3
Go	github.com/hashicorp/vault	from 1.17.0-rc1 · before 1.17.0	1.17.0

Same product

hashicorp: all records

Other highest-scoring records for the same primary product.

CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.
40Plan
CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates
39Monitor
CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials
39Monitor

Published before and after this one in the same product

← EarlierCVE-2024-2660Apr 4, 2024 · Vault TLS Cert Auth Method Did Not Correctly Validate OCSP Responses
27Monitor
← EarlierCVE-2024-2877Apr 30, 2024 · Vault Enterprise Leaks Sensitive HTTP Request Headers in the Audit Log When Deployed With a Performance Standby Node
22Monitor
Later →CVE-2024-6468Jul 11, 2024 · Vault Vulnerable to Denial of Service When Setting a Proxy Protocol Behavior
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
HashiCorp Vault	1.14.13	Vendor (CNA)
HashiCorp Vault	1.15.9	Vendor (CNA)
HashiCorp Vault	1.16.2	Vendor (CNA)
HashiCorp Vault Enterprise	1.14.13	Vendor (CNA)
HashiCorp Vault Enterprise	1.15.9	Vendor (CNA)
HashiCorp Vault Enterprise	1.16.2	Vendor (CNA)
Go:github.com/hashicorp/vault	1.15.9	Package registry (OSV)
Go:github.com/hashicorp/vault	1.16.3	Package registry (OSV)
Go:github.com/hashicorp/vault	1.17.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0722 · Jun 14, 2024(HashiCorp Vault Güvenlik Bildirimi )

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records