{"answers":{"affected":"4 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-6013 in the wild and no public exploit code.","fix":"Upgrade github.com/hashicorp/vault to 1.20.2 or later.","what":"CVE-2025-6013 is a medium-severity authentication bypass vulnerability in Hashicorp Vault, published on 6 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6013 and fix it if it is affected.\n\nWhat it is: CVE-2025-6013 is a medium-severity authentication bypass vulnerability in Hashicorp Vault, published on 6 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6013 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.20.2\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.20.2\n- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.20.2\n- vault (Bitnami): affected from 1.10.0; fixed in 1.20.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-6013/ (Markdown: https://insights.sbomify.com/CVE-2025-6013/index.md)","id":"CVE-2025-6013","markdown":"https://insights.sbomify.com/CVE-2025-6013/index.md","name":"CVE-2025-6013","record":{"aliases":["BIT-vault-2025-6013","GHSA-7rx2-769v-hrwf","GO-2025-3848","MINI-rf9r-m9w5-w4qv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"HashiCorp Vault","requires_auth":"high_privilege","summary":"Attackers can bypass MFA enforcement in Vault's LDAP auth method when username_as_alias is enabled and specific CN formatting exists.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[{"product":"vault","vendor":"hashicorp"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-156","name":"Improper Neutralization of Whitespace"}],"description":"Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if username_as_alias was set to true and a user had multiple CNs that are equal but with leading or trailing spaces. Fixed in Vault Community Edition 1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Vault LDAP MFA Enforcement Bypass When Using Username As Alias","id":"CVE-2025-6013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"hashicorp:vault","products":["hashicorp:vault"],"type":"auth_bypass","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"Vault TOTP Secrets Engine Code Reuse","id":"CVE-2025-6014"},"packages":[{"ecosystem":"Bitnami","fixed":["1.20.2"],"introduced":["1.10.0"],"last_affected":[],"package":"vault","purl":"pkg:bitnami/vault","source":"BIT-vault-2025-6013"},{"ecosystem":"Go","fixed":["1.20.2"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":null,"source":"GHSA-7rx2-769v-hrwf"},{"ecosystem":"Go","fixed":["1.20.2"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GHSA-7rx2-769v-hrwf"},{"ecosystem":"Go","fixed":["1.20.2"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vault","purl":"pkg:golang/github.com/hashicorp/vault","source":"GO-2025-3848"}],"prev":{"headline":"Auto Attachments \u003c= 1.8.5 - Authenticated (Administrator+) Stored Cross-Site Scripting","id":"CVE-2025-6012"},"products":["Vault","Vault Enterprise"],"published":"2025-08-06","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-35192","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.8,"headline":"Improper Input Validation in HashiCorp Vault","id":"CVE-2020-12757","kev_date_added":null,"published":"2020-06-10"},{"cvss_score":9.1,"headline":"Arbitrary Remote Code Execution via Plugin Catalog Abuse","id":"CVE-2025-6000","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":9.1,"headline":"HashiCorp Vault vulnerable to incorrect metadata access","id":"CVE-2022-40186","kev_date_added":null,"published":"2022-09-22"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2022-36129","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":9.1,"headline":"HashiCorp Vault Improper Privilege Management","id":"CVE-2020-10661","kev_date_added":null,"published":"2020-03-23"},{"cvss_score":8.2,"headline":"Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault","id":"CVE-2020-16250","kev_date_added":null,"published":"2020-08-26"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["HashiCorp"]},"summary":"Attackers can bypass MFA enforcement in Vault's LDAP auth method when username_as_alias is enabled and specific CN formatting exists.","url":"https://insights.sbomify.com/CVE-2025-6013/"}