How severe is CVE-2026-4525?

CVE-2026-4525 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-4525 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-4525?

CVE-2026-4525 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-4525?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-4525 have an EU (EUVD) identifier?

Yes. CVE-2026-4525 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-23345.

When was CVE-2026-4525 published?

CVE-2026-4525 was published on 2026-04-17 and last updated on 2026-06-30.

CVE-2026-4525

CVE-2026-4525 is a high-severity vulnerability in Hashicorp Vault with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-201.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-23345
Weakness: CWE-201
Affected product: Hashicorp Vault
Published: 2026-04-17
Last modified: 2026-06-30

Description

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.

Frequently asked questions

What is CVE-2026-4525?: 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.
How severe is CVE-2026-4525?: CVE-2026-4525 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-4525 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-4525?: CVE-2026-4525 primarily affects Hashicorp Vault. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-4525?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-4525 have an EU (EUVD) identifier?: Yes. CVE-2026-4525 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-23345.
When was CVE-2026-4525 published?: CVE-2026-4525 was published on 2026-04-17 and last updated on 2026-06-30.

References

Affected products (2)

cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*

More vulnerabilities in Hashicorp Vault

CVE-2020-35192 — Critical (CVSS 9.8): The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker…
CVE-2020-12757 — Critical (CVSS 9.8): HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly…
CVE-2025-6000 — Critical (CVSS 9.1): A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution…
CVE-2022-40186 — Critical (CVSS 9.1): An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine…
CVE-2022-36129 — Critical (CVSS 9.1): HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an…
CVE-2020-10661 — Critical (CVSS 9.1): HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing…

All CVEs affecting Hashicorp Vault →

Other CWE-201 vulnerabilities

CVE-2025-49408 — Critical (CVSS 10.0): Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded…
CVE-2024-7205 — Critical (CVSS 9.4): When the device is shared, the homepage module are before 2.19.0 in eWeLink Cloud Service allows Secondary user to…
CVE-2026-39912 — Critical (CVSS 9.1): V2Board 1.6.1 through 1.7.4 and Xboard through 0.1.9 expose authentication tokens in HTTP response bodies of the…
CVE-2025-48749 — Critical (CVSS 9.1): Netwrix Directory Manager (formerly Imanami GroupID) v11.0.0.0 and before & after v.11.1.25134.03 inserts Sensitive…
CVE-2025-11500 — High (CVSS 8.7): Tinycontrol devices such as tcPDU and LAN Controllers LK3.5, LK3.9 and LK4 have two separate authentication…
CVE-2025-48045 — High (CVSS 8.7): An unauthenticated HTTP GET request to the /client.php endpoint will disclose the default administrator user…

Browse all CWE-201 vulnerabilities →