Skip to content
Noroxi
NVD / CVE Program· CNA HashiCorp

CVE-2025-4166: Vault May Include Sensitive Data in Error Logs When Using the KV v2 Plugin

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/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.45% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: HashiCorp Vault 1.19.2; HashiCorp Vault Enterprise 1.16.20, 1.17.16, 1.18.9.
  • Severity is disputed: the assigning authority (CNA) scores it 4.5, NVD 6.5.

Low priority for now. Upgrade to HashiCorp Vault 1.19.2; HashiCorp Vault Enterprise 1.16.20, 1.17.16, 1.18.9 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 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.

Published
May 2, 2025
Updated
Jun 17, 2026
EPSS
0.4% · 40th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.5
CNA · HashiCorp
4.5
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/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.

Follow CVE-2025-4166

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
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.

VendorProduct
hashicorpvault
openbaoopenbao

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.3.0 and later · before 1.19.2affected · semver
  • HashiCorp Vault Enterprise

    • 0.10.0 and later · before 1.19.2affected · semverfixed in 1.18.9, 1.17.16, 1.16.20

Package-level exposure

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

EcosystemPackageAffected rangeFix
Alpine:v3.22openbaobefore 2.2.2-r02.2.2-r0
Gogithub.com/hashicorp/vaultfrom 0.3.0 · before 1.19.31.19.3
openSUSE:Tumbleweedgovulncheck-vulndbbefore 0.0.20250506T153719-1.10.0.20250506T153719-1.1
openSUSE:Tumbleweedopenbaobefore 2.2.2-1.12.2.2-1.1

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-7594Sep 26, 2024 · Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
    35Monitor
  • ← EarlierCVE-2024-8185Oct 31, 2024 · Vault Vulnerable to Denial of Service When Processing Raft Join Requests
    30Monitor
  • Later →CVE-2025-3879May 2, 2025 · Vault’s Azure Authentication Method bound_location Restriction Could be Bypassed on Login
    35Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
HashiCorp Vault1.19.2Vendor (CNA)
HashiCorp Vault Enterprise1.16.20Vendor (CNA)
HashiCorp Vault Enterprise1.17.16Vendor (CNA)
HashiCorp Vault Enterprise1.18.9Vendor (CNA)
HashiCorp Vault Enterprise1.19.2Vendor (CNA)
alpine:openbao2.2.2-r0 · Alpine:v3.22Package registry (OSV)
Go:github.com/hashicorp/vault1.19.3Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20250506T153719-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:openbao2.2.2-1.1 · openSUSE:TumbleweedPackage 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

nvd-primary

Attack context

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

References

All records