Skip to content
Fencer Intel
medium 4.4

CVE-2026-5051 json

Audit Log Plugin Directory Guard Bypass via Legacy path Option

published 4mo ago modified 4mo ago also BIT-vault-2026-5051 , EUVD-2026-41098

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

Summary

HashiCorp Vault and Vault Enterprise prior to 2.0.1 audit device validation logic did not consistently apply plugin directory protections when the legacy file audit path option was used.

This vulnerability (CVE-2026-5051) is fixed in 2.0.1, 1.21.6, 1.20.11, and 1.19.17.

Patch / fix

  • bitnami vault 1.19.17, 1.20.11, 1.21.6, 2.0.1
  • HashiCorp Vault 1.20.11, 1.21.6, 2.0.1
  • HashiCorp Vault Enterprise 1.19.17, 1.20.11, 1.21.6, 2.0.1

Is CVE-2026-5051 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-2026-5051 updated cvss 4.4

Vault: Vault Enterprise: HashiCorp Vault: Audit device validation bypass via legacy file audit path option

  • Red Hat OpenShift Container Platform 4 openshift4/ose-installer-rhel9, openshift4/ose-baremetal-installer-rhel9 Red Hat Openshift Data Foundation 4 odf4/cephcsi-rhel9, odf4/mcg-cli-rhel9, odf4/odf-cli-rhel9, odf4/mcg-rhel9-operator
    not affected: vulnerable code not present

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
4mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 4.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami vault
>=1.19.0, <1.19.17
>=1.20.0, <1.20.11
>=1.21.0, <1.21.6
>=2.0.0, <2.0.1
1.19.17
1.20.11
1.21.6
2.0.1

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.