Skip to content
Fencer Intel
medium 4.5

CVE-2025-4166 json

Vault May Include Sensitive Data in Error Logs When Using the KV v2 Plugin

published last yr. modified last mo. also BIT-openbao-2025-4166 , BIT-vault-2025-4166 , EUVD-2025-13240 , GHSA-gcqf-f89c-68hv , GO-2025-3663

cvss
4.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

Vault Community and Vault Enterprise Key/Value (kv) Version 2 plugin may unintentionally expose sensitive information in server and audit logs when users submit malformed payloads during secret creation or update operations via the Vault REST API. This vulnerability, identified as CVE-2025-4166, is fixed in Vault Community 1.19.3 and Vault Enterprise 1.19.3, 1.18.9, 1.17.16, 1.16.20.

Patch / fix

  • go github.com/hashicorp/vault 1.19.3
  • bitnami openbao 2.2.2
  • bitnami vault 1.19.3
  • HashiCorp Vault 1.19.2
  • HashiCorp Vault Enterprise 1.16.20, 1.17.16, 1.18.9, 1.19.2
  • openbao openSUSE Tumbleweed 2.2.2-1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250506T153719-1.1

opensuse advisories openSUSE-SU-2025:15186-1openSUSE-SU-2025:15059-1

  • openbao Alpine 3.24, Alpine 3.23, Alpine 3.22 2.2.2-r0

alpine advisories ALPINE-CVE-2025-4166

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2025-4166 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-4166 updated cvss 4.5

vault: Vault May Include Sensitive Data in Error Logs When Using the KV v2 Plugin

  • Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=0.3.0, <1.19.3
1.19.3
bitnami openbao
<2.2.2
2.2.2
bitnami vault
>=0.3.0, <1.19.3
1.19.3

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.