Medium [CVE-2026-5051] Audit device validation bypass via legacy file audit path option
This medium-severity Red Hat Linux advisory covers CVE-2026-5051.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
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.
This inconsistency could allow an attacker to bypass security controls, potentially leading to unauthorized access to sensitive information. Red Hat products that bundle the Vault Go client library (github.com/hashicorp/vault/api) are not affected because they only use the client SDK to connect to external Vault servers for secrets/KMS operations.
The vulnerable code is in the Vault server's audit subsystem (vault/audit, vault/vault, vault/builtin packages), which is not imported or executed by any Red Hat product. Red Hat severity: Moderate — CVSS 4.4 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N).
Weakness: CWE-807. Red Hat lists Red Hat OpenShift Container Platform 4; Red Hat Openshift Data Foundation 4 as not affected.
Is CVE-2026-5051 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-5051 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-5051?
Upgrade to a fixed release named by Red Hat:
- 2.0.1
- 1.21.6
- 1.20.11
- 1.19.17
Confirm against the vendor advisory before you patch.
- < 2.0.1
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 2.0.1
- 1.21.6
- 1.20.11
- 1.19.17
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.