CVE-2024-8365 | Vault Leaks AppRole Client Tokens And Accessor in Audit Log

Vault Community Edition and Vault Enterprise experienced a regression where functionality that HMAC’d sensitive headers in the configured audit device, specifically client tokens and token accessors, was removed. This resulted in the plaintext values of client tokens and token accessors being stored in the audit log. This vulnerability, CVE-2024-8365, was fixed in Vault Community Edition and Vault Enterprise 1.17.5 and Vault Enterprise 1.16.9.

Published: 2024-09-02 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-8365 is rated Low Risk (38/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.47%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-8365

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.26% 0.47% +0.22%
2 2025-12-28 0.24% 0.26% +0.01%
3 2025-12-27 0.24%

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-8365

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.2 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.7 4.0 [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 3.6 [email protected]

Weakness enumeration for CVE-2024-8365

GitHub Security Advisory for CVE-2024-8365

GHSA-jjxf-26c9-77gm · Severity: medium · Ecosystem: go — Vault Leaks Client Token and Token Accessor in Audit Devices

OS Trackers for CVE-2024-8365

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2024-8365

Affected software / configurations for CVE-2024-8365

Vendor Product Version Raw CPE
hashicorp vault < 1.16.9 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
hashicorp vault < 1.17.5 cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
hashicorp vault >= 1.17.0, < 1.17.5 cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

References for CVE-2024-8365

cvelogic Threat Intelligence