Skip to main content
CVE-2024-2877VulnerabilityPublished Updated

CVE-2024-2877: Vault Enterprise Leaks Sensitive HTTP Request Headers in the Audit Log When Deployed With a Performance Standby Node

Affects vaultSource GCVE Database

0

Not known to be exploited : upgrade to 1.15.8 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.15.8

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade vault to 1.15.8.

Affected software

ProductAffectedFixed in
Bitnamivaultpkg:bitnami/vaultOther threatsAffected
  • >=1.15.0 <1.15.8
Fixed in
  • 1.15.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vault Enterprise to version 1.15.8 or later, where this vulnerability has been fixed. No additional mitigation steps are required once the patch is applied.

Description

Vault Enterprise versions 1.15.0 through 1.15.7, when configured with performance standby nodes and an audit device, inadvertently log sensitive HTTP request headers in cleartext on the standby node. This vulnerability, identified as CVE-2024-2877, risks exposure of sensitive information through audit logs. The issue was fixed in version 1.15.8.

References

Community reviews

Loading reviews…