CVE-2022-41316 — vault
MEDIUMCVE-2022-41316 is a medium-severity (CVSS 5.3) CWE-295 vulnerability in github.com/hashicorp/vault. A fix is available for github.com/hashicorp/vault — see the affected versions and patch details below.
HashiCorp Vault's revocation list not respected
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-41316.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/hashicorp/vault🐹github.com/hashicorp/vault🐹github.com/hashicorp/vaultReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hashicorp/vault | ≥ 1.11.0&&< 1.11.4 | 1.11.4go get github.com/hashicorp/vault@v1.11.4 |
| 🐹Go | github.com/hashicorp/vault | ≥ 1.10.0&&< 1.10.7 | 1.10.7go get github.com/hashicorp/vault@v1.10.7 |
| 🐹Go | github.com/hashicorp/vault | all versions | 1.9.10go get github.com/hashicorp/vault@v1.9.10 |
Affected Products
vaulthashicorpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/vault, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hashicorp/vault to 1.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41316 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.12 | openshift4/ose-installer:v4.12.0-202301090455.p0.gba94031.assembly.stream | RHSA-2022:7399 |
| Red Hat OpenShift Container Platform 4.13 | openshift4/ose-installer:v4.13.0-202305091542.p0.g44db7b2.assembly.stream | RHSA-2023:1326 |
| RHODF-4.13-RHEL-9 | odf4/mcg-rhel9-operator:v4.13.0-41 | RHSA-2023:3742 |
Frequently Asked Questions
Is CVE-2022-41316 in your dependencies?
Find it across Go, including transitive dependencies.