Skip to content
Fencer Intel
high 7.5

CVE-2026-4525 json

Vault Token Leaked to Backends via Authorization: Bearer Passthrough Header

published 6mo ago modified 15d ago also BIT-vault-2026-4525 , EUVD-2026-23345 , GHSA-72gw-fmmr-c4r4 , GO-2026-5199

cvss
7.5
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 35%
public exploits
0
none known

Summary

If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Patch / fix

  • bitnami vault 2.0.0
  • HashiCorp Vault 2.0.0
  • HashiCorp Vault Enterprise 1.19.16, 1.20.10, 1.21.5, 2.0.0
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-4525 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-4525 updated cvss 7.5

Vault: Vault: Information disclosure of authentication tokens via incorrect header handling

  • Red Hat Openshift Data Foundation 4 mcg-cli-rhel9, mcg-rhel8-operator, mcg-rhel9-operator, odf4/mcg-cli-rhel9, odf4/mcg-rhel8-operator, odf4/mcg-rhel9-operator
    affected: workaround, no fix available
  • Red Hat OpenShift Container Platform 4 openshift4/ose-installer-rhel9, openshift4/ose-baremetal-installer-rhel9
    not affected: vulnerable code not present
  • Red Hat Openshift Data Foundation 4 cephcsi-rhel8, cephcsi-rhel9, ocs4/cephcsi-rhel8, odf4/cephcsi-rhel8, odf4/cephcsi-rhel9
    not affected: vulnerable code not in execute path

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
total
Assessed
6mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/vault
>=0.11.2, <=1.21.4
>=0.11.2
 no fix listed
bitnami vault
>=0.10.0, <2.0.0
2.0.0

Affected products

  • HashiCorp Vault
  • HashiCorp Vault Enterprise
  • Red Hat Red Hat OpenShift Container Platform 4
  • Red Hat Red Hat Openshift Data Foundation 4

Classification

Weakness
  • CWE-201 Insertion of Sensitive Information Into Sent Data

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.