# CVE-2022-41316: HashiCorp Vault's revocation list not respected

> Attackers can bypass certificate revocation checks in HashiCorp Vault if CRLs are not loaded at startup, allowing revoked certificates to remain valid.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** BIT-vault-2022-41316, GHSA-9mh8-9j64-443f, GO-2023-1897

## What is CVE-2022-41316?

CVE-2022-41316 is a medium-severity vulnerability in Hashicorp Vault, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA into memory on startup, resulting in the revocation list not being checked if the CRL has not yet been retrieved. Fixed in 1.12.0, 1.11.4, 1.10.7, and 1.9.10.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-41316?

8 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault` | Go | All versions | 1.9.10, 1.10.7, 1.11.4 |
| `github.com/hashicorp/vault` | Go | All versions | 1.9.10 |
| `github.com/hashicorp/vault` | Go | All versions | 1.9.10 |
| `github.com/hashicorp/vault` | Go | From 1.10.0 | 1.10.7 |
| `github.com/hashicorp/vault` | Go | From 1.10.0 | 1.10.7 |
| `github.com/hashicorp/vault` | Go | From 1.11.0 | 1.11.4 |
| `github.com/hashicorp/vault` | Go | From 1.11.0 | 1.11.4 |
| `vault` | Bitnami | All versions | 1.9.10, 1.10.7, 1.11.4 |

Products: Hashicorp Vault.

## How do I fix CVE-2022-41316?

Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.9.10, 1.10.7 or 1.11.4.

## Is CVE-2022-41316 being exploited?

There is no known exploitation of CVE-2022-41316 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-12757](https://insights.sbomify.com/CVE-2020-12757/): Improper Input Validation in HashiCorp Vault (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41316 and fix it if it is affected.

What it is: CVE-2022-41316 is a medium-severity vulnerability in Hashicorp Vault, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41316 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.9.10, 1.10.7, 1.11.4
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.9.10
- github.com/hashicorp/vault (Go): affected all versions; fixed in 1.9.10
- github.com/hashicorp/vault (Go): affected from 1.10.0; fixed in 1.10.7
- github.com/hashicorp/vault (Go): affected from 1.10.0; fixed in 1.10.7
- github.com/hashicorp/vault (Go): affected from 1.11.0; fixed in 1.11.4
- github.com/hashicorp/vault (Go): affected from 1.11.0; fixed in 1.11.4
- vault (Bitnami): affected all versions; fixed in 1.9.10, 1.10.7, 1.11.4

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41316/ (Markdown: https://insights.sbomify.com/CVE-2022-41316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41316
- OSV: https://osv.dev/vulnerability/CVE-2022-41316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41316/
Summaries are generated and may contain mistakes; the official description above is the record.