Advisory record · GHSA-r3w7-mfpm-c2vw

Incorrect TLS certificate auth method in Vault

CVSS 8.1 HighEPSS 0.0045 · 39th percentile

Published by the GitHub Advisory Database at 4 Mar 2024, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/hashicorp/vaultGo>=1.15.0, <1.15.5 || <1.14.101.15.5, 1.14.10
Identifiers
GHSA-r3w7-mfpm-c2vw · BIT-vault-2024-2048 · CVE-2024-2048 · GO-2024-2617
Weakness (CWE)
CWE-295
Published
4 Mar 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Go package github.com/hashicorp/vault is affected in versions before 1.14.10 and from 1.15.0 before 1.15.5. The TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as the trusted certificate. An attacker who can present a crafted certificate may be able to bypass authentication. Upgrade to 1.14.10 or 1.15.5.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (HashiCorp)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.