Vulnerabilities in pkg:golang/github.com/hashicorp/vault
PACKAGECVE-2026-5052 is a MODERATE (CVSS 5.3) hashicorp vault has server-side request vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Github.com/hashicorp/vault libraries in the Go ecosystem. The issue involves hashicorp vault has server-side request forgery in acme challenge validation via attacker-controlled dns. Remediation is available in the latest vendor maintenance releases.
pkg:golang/github.com/hashicorp/vault
Vulnerability advisories affecting package pkg:golang/github.com/hashicorp/vault. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-8r5m-3f66-qpr3 | CVE-2026-5052 | MODERATE | HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS |
| GHSA-88v5-9hxc-f85r | CVE-2026-5807 | HIGH | HashiCorp Vault Vulnerable to Denial-of-Service via Unauthenticated Root Token Generation/Rekey Operations |
| GHSA-72gw-fmmr-c4r4 | CVE-2026-4525 | HIGH | HashiCorp Vault May Expose Tokens to Auth Plugins Due to Incorrect Header Sanitization |
| GHSA-m2w4-8ggf-rj47 | CVE-2026-3605 | HIGH | HashiCorp Vault has a KVv2 Metadata and Secret Deletion Policy Bypass that leads to Denial-of-Service |
| GHSA-57gg-cj55-q5g2 | CVE-2020-25816 | CRITICAL | Token leases could outlive their TTL in HashiCorp Vault |
| GHSA-9g4h-h484-3578 | CVE-2025-11621 | HIGH | HashiCorp Vault and Vault Enterprise's AWS Auth method may be susceptible to authentication bypass |
| GHSA-vp5w-xcfc-73wf | CVE-2025-12044 | HIGH | Hashicorp Vault and Vault Enterprise vulnerable to a denial of service when processing JSON |
| GHSA-8f82-53h8-2p34 | CVE-2025-6203 | HIGH | HashiCorp Vault Community Edition Denial of Service Though Complex JSON Payloads |
| GHSA-jg74-mwgw-v6x3 | CVE-2024-7594 | HIGH | Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default |
| GHSA-32cj-5wx4-gq8p | CVE-2024-5798 | LOW | HashiCorp Vault Incorrectly Validated JSON Web Tokens (JWT) Audience Claims |
| GHSA-7rx2-769v-hrwf | CVE-2025-6013 | MODERATE | HashiCorp Vault ldap auth method may not have correctly enforced MFA |
| GHSA-r3w7-mfpm-c2vw | CVE-2024-2048 | HIGH | Incorrect TLS certificate auth method in Vault |
| GHSA-g233-2p4r-3q7v | CVE-2024-8185 | HIGH | Hashicorp Vault vulnerable to denial of service through memory exhaustion |
| GHSA-rr8j-7w34-xp5j | CVE-2024-9180 | HIGH | Vault Community Edition privilege escalation vulnerability |
| GHSA-6c5r-4wfc-3mcx | CVE-2025-6037 | MODERATE | Hashicorp Vault has Incorrect Validation for Non-CA Certificates |
| GHSA-v6r4-35f9-9rpw | CVE-2025-6015 | MODERATE | Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability |
| GHSA-qv3p-fmv3-9hww | CVE-2025-6014 | MODERATE | Hashicorp Vault's TOTP Secrets Engine Susceptible to Code Reuse |
| GHSA-mwgr-84fv-3jh9 | CVE-2025-6011 | LOW | Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users |
| GHSA-qgj7-fmq2-6cc4 | CVE-2025-6004 | MODERATE | Hashicorp Vault has Lockout Feature Authentication Bypass |
| GHSA-6h4p-m86h-hhgh | CVE-2025-5999 | HIGH | Hashicorp Vault has Privilege Escalation Vulnerability |
| GHSA-mr4h-qf9j-f665 | CVE-2025-6000 | CRITICAL | Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration |
| GHSA-fhc2-8qx8-6vj7 | CVE-2025-4656 | LOW | Vault Community Edition rekey and recovery key operations can cause denial of service |
| GHSA-7cgv-v83v-rr87 | CVE-2022-40186 | CRITICAL | HashiCorp Vault vulnerable to incorrect metadata access |
| GHSA-9mh8-9j64-443f | CVE-2022-41316 | MODERATE | HashiCorp Vault's revocation list not respected |
| GHSA-f9ch-h8j7-8jwg | CVE-2025-3879 | MODERATE | Hashicorp Vault Community vulnerable to Incorrect Authorization |
| GHSA-gcqf-f89c-68hv | CVE-2025-4166 | MODERATE | Hashicorp Vault Community vulnerable to Generation of Error Message Containing Sensitive Information |
| GHSA-6p62-6cg9-f5f5 | CVE-2023-6337 | HIGH | Memory exhaustion in HashiCorp Vault |
| GHSA-j2rp-gmqv-frhv | CVE-2024-2660 | MODERATE | HashiCorpVault does not correctly validate OCSP responses |
| GHSA-m979-w9wj-qfj9 | CVE-2020-10660 | MODERATE | HashiCorp Vault Improper Privilege Management |
| GHSA-4mp7-2m29-gqxf | CVE-2020-16251 | HIGH | HashiCorp Vault Authentication bypass |
| GHSA-j6vv-vv26-rh7c | CVE-2020-10661 | CRITICAL | HashiCorp Vault Improper Privilege Management |
| GHSA-jjxf-26c9-77gm | CVE-2024-8365 | MODERATE | Vault Leaks Client Token and Token Accessor in Audit Devices |
| GHSA-2qmw-pvf7-4mw6 | CVE-2024-6468 | HIGH | Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions |
| GHSA-vgh3-mwxq-rcp8 | CVE-2024-0831 | MODERATE | Hashicorp Vault may expose sensitive log information |
| GHSA-rq95-xf66-j689 | CVE-2021-3282 | HIGH | Improper Authentication in HashiCorp Vault |
| GHSA-rpgp-9hmg-j25x | CVE-2020-35177 | MODERATE | Enumeration of users in HashiCorp Vault |
| GHSA-4qhc-v8r6-8vwm | CVE-2023-5954 | HIGH | HashiCorp Vault Missing Release of Memory after Effective Lifetime vulnerability |
| GHSA-25xj-89g5-fm6h | CVE-2020-13223 | HIGH | Information Disclosure in HashiCorp Vault |
| GHSA-86c6-3g63-5w64 | CVE-2023-5077 | HIGH | Hashicorp Vault Incorrect Permission Assignment for Critical Resource vulnerability |
| GHSA-v84f-6r39-cpfc | CVE-2023-4680 | MODERATE | HashiCorp Vault Improper Input Validation vulnerability |
| GHSA-fp52-qw33-mfmw | CVE-2020-16250 | HIGH | Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault |
| GHSA-9v3w-w2jh-4hff | CVE-2023-3462 | MODERATE | HashiCorp Vault and Vault Enterprise vulnerable to user enumeration |
| GHSA-wmg5-g953-qqfw | CVE-2023-24999 | HIGH | Hashicorp Vault Fails to Verify if Approle SecretID Belongs to Role During a Destroy Operation |
| GHSA-gq98-53rq-qr5h | CVE-2023-2121 | MODERATE | Hashicorp Vault vulnerable to Cross-site Scripting |
| GHSA-vq4h-9ghm-qmrr | CVE-2023-25000 | MODERATE | HashiCorp Vault's implementation of Shamir's secret sharing vulnerable to cache-timing attacks |
| GHSA-hwc3-3qh6-r4gg | CVE-2023-0665 | MODERATE | HashiCorp Vault's PKI mount vulnerable to denial of service |
| GHSA-v3hp-mcj5-pg39 | CVE-2023-0620 | MODERATE | HashiCorp Vault’s Microsoft SQL Database Storage Backend Vulnerable to SQL Injection Via Configuration File |
| GHSA-23fq-q7hc-993r | CVE-2021-38553 | CRITICAL | HashiCorp Vault underlying database had excessively broad filesystem permissions from v1.4.0 until v1.8.0 |
| GHSA-qv95-g3gm-x542 | CVE-2021-41802 | LOW | Hashicorp Vault Privilege Escalation Vulnerability |
| GHSA-pfmw-vj74-ph8g | CVE-2021-43998 | CRITICAL | HashiCorp Vault Incorrect Permission Assignment for Critical Resource |
| GHSA-c5wc-v287-82pc | CVE-2022-30689 | MODERATE | HashiCorp Vault improper configuration of multi factor authentication |
| GHSA-6239-28c2-9mrm | CVE-2021-38554 | MODERATE | Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault |
| GHSA-362v-wg5p-64w2 | CVE-2021-42135 | HIGH | Incorrect Privilege Assignment in HashiCorp Vault |
| GHSA-9vh5-r4qw-v3vv | CVE-2020-7220 | HIGH | Improper Resource Shutdown or Release in HashiCorp Vault |
| GHSA-38j9-7pp9-2hjw | CVE-2021-32923 | HIGH | Invalid session token expiration |
CVE-2026-5052 at a Glance
Security Impact
CVSS: 5.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-5052
To remediate this vulnerability, upgrade all affected Github.com/hashicorp/vault dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/hashicorp/vault to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/hashicorp/vault
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-5052, inspect your project dependencies for Github.com/hashicorp/vault:
inspect dependencies for github.com/hashicorp/vault
Analyze the terminal output to locate any version of Github.com/hashicorp/vault in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Github.com/hashicorp/vault, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-5052 Affected Github.com/hashicorp/vault Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/hashicorp/vault
|
Go |
≥ 1.14.0
≤ 1.21.4
|
|
References
Frequently Asked Questions
What is CVE-2026-5052?
Which Github.com/hashicorp/vault versions are affected?
What version fixes CVE-2026-5052?
Is github.com/hashicorp/vault affected?
What is the CVSS score of CVE-2026-5052?
What CWE is associated with CVE-2026-5052?
How can I check Go dependencies for CVE-2026-5052?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8r5m-3f66-qpr3",
"modified" : "2026-07-21T13:57:05Z",
"published" : "2026-04-17T06:31:07Z",
"aliases" : [ "CVE-2026-5052" ],
"summary" : "HashiCorp Vault has Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS",
"details" : "Vault’s PKI engine’s ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. This may lead to these requests being sent to local network targets, potentially leading to information disclosure. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/hashicorp/vault"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.14.0"
}, {
"last_affected" : "1.21.4"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-5052"
}, {
"type" : "WEB",
"url" : "https://discuss.hashicorp.com/t/hcsec-2026-06-vault-vulnerable-to-server-side-request-forgery-in-acme-challenge-validation-via-attacker-controlled-dns/77343"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-8r5m-3f66-qpr3"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/hashicorp/vault"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-18T00:53:25Z",
"nvd_published_at" : "2026-04-17T04:16:12Z"
}
}