Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

cve-program · severity unknownEUVD CVSS 3.1 5.3 CVSS 3.1 · [email protected] · Primary 5.3 MEDIUMCVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 5.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/hashicorp/vault 1.11.4Fixed by github.com/hashicorp/vault 1.10.7Fixed by github.com/hashicorp/vault 1.9.10osv · severity unknownFixed by github.com/hashicorp/vault 1.9.10Fixed by github.com/hashicorp/vault 1.10.7Fixed by github.com/hashicorp/vault 1.11.4KEV status unknown

cve-program · CVE-2022-41316

Published

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.

Read the publisher's advisory

euvd · EUVD-2023-2017

Published

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.

Read the publisher's advisory

nvd · CVE-2022-41316

Published

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.

Read the publisher's advisory

osv · GHSA-9mh8-9j64-443f

Published

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.

Read the publisher's advisory

osv · GO-2023-1897

Published

HashiCorp Vault's revocation list not respected in github.com/hashicorp/vault

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2022-41316

Published

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 ye…

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.

Source published
12 Oct 2022 00:00:00 UTC
Source modified
15 May 2025 14:59:25 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2023-2017

Published

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 ye…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 12, 2022, 12:00:00 AM

dateUpdated: May 15, 2025, 2:59:25 PM

4 related source bulletins · separate from aliases

RHSA-2022:7399: Red Hat Security Advisory: OpenShift Container Platform 4.12.0 bug fix and security update

CVE-2021-38561 · CVE-2022-1705 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-21698 · CVE-2022-32148 · CVE-2022-32190 · CVE-2022-41316 · CVE-2022-41715 · CVE-2023-0296

RHSA-2023:1326: Red Hat Security Advisory: OpenShift Container Platform 4.13.0 security update

CVE-2021-4235 · CVE-2021-4238 · CVE-2021-20329 · CVE-2021-38561 · CVE-2022-21698 · CVE-2022-23525 · CVE-2022-23526 · CVE-2022-27191 · CVE-2022-41316 · CVE-2022-41717 · CVE-2022-41721 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-46146 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-25000 · CVE-2023-25165 · CVE-2023-25173 · CVE-2023-25809 · CVE-2023-27561 · CVE-2023-28642 · CVE-2023-30841

RHSA-2023:3742: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.13.0 security and bug fix update

CVE-2020-16250 · CVE-2020-16251 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-4235 · CVE-2021-4238 · CVE-2021-43998 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-3517 · CVE-2022-21824 · CVE-2022-23540 · CVE-2022-23541 · CVE-2022-27664 · CVE-2022-30635 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-38149 · CVE-2022-38900 · CVE-2022-41316 · CVE-2022-41715 · CVE-2022-41717 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-46175 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-24999 · CVE-2023-25000

WID-SEC-W-2023-1542: Red Hat OpenShift: Mehrere Schwachstellen

CVE-2015-20107 · CVE-2018-25032 · CVE-2020-10735 · CVE-2020-16250 · CVE-2020-16251 · CVE-2020-17049 · CVE-2021-28861 · CVE-2021-3765 · CVE-2021-3807 · CVE-2021-4231 · CVE-2021-4235 · CVE-2021-4238 · CVE-2021-43519 · CVE-2021-43998 · CVE-2021-44531 · CVE-2021-44532 · CVE-2021-44533 · CVE-2021-44964 · CVE-2021-46828 · CVE-2021-46848 · CVE-2022-0670 · CVE-2022-1271 · CVE-2022-1304 · CVE-2022-1348 · CVE-2022-1586 · CVE-2022-1587 · CVE-2022-21824 · CVE-2022-2309 · CVE-2022-23540 · CVE-2022-23541 · CVE-2022-24903 · CVE-2022-2509 · CVE-2022-26280 · CVE-2022-27664 · CVE-2022-2795 · CVE-2022-2879 · CVE-2022-2880 · CVE-2022-28805 · CVE-2022-29154 · CVE-2022-30635 · CVE-2022-3094 · CVE-2022-31129 · CVE-2022-32189 · CVE-2022-32190 · CVE-2022-33099 · CVE-2022-3358 · CVE-2022-34903 · CVE-2022-3515 · CVE-2022-3517 · CVE-2022-35737 · CVE-2022-36227 · CVE-2022-3715 · CVE-2022-3736 · CVE-2022-37434 · CVE-2022-38149 · CVE-2022-3821 · CVE-2022-38900 · CVE-2022-3924 · CVE-2022-40023 · CVE-2022-40303 · CVE-2022-40304 · CVE-2022-40897 · CVE-2022-41316 · CVE-2022-41715 · CVE-2022-41717 · CVE-2022-41723 · CVE-2022-41724 · CVE-2022-41725 · CVE-2022-42010 · CVE-2022-42011 · CVE-2022-42012 · CVE-2022-42898 · CVE-2022-42919 · CVE-2022-43680 · CVE-2022-4415 · CVE-2022-45061 · CVE-2022-45873 · CVE-2022-46175 · CVE-2022-47024 · CVE-2022-47629 · CVE-2022-48303 · CVE-2022-48337 · CVE-2022-48338 · CVE-2022-48339 · CVE-2023-0361 · CVE-2023-0620 · CVE-2023-0665 · CVE-2023-22809 · CVE-2023-24329 · CVE-2023-2491 · CVE-2023-24999 · CVE-2023-25000 · CVE-2023-25136

Source published
Oct 12, 2022, 12:00:00 AM (timezone not stated)
Source modified
May 15, 2025, 2:59:25 PM (timezone not stated)
Saved here
18 Nov 2026 03:33:07 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

nvd · CVE-2022-41316

Published

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 ye…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-295

Original publisher date fields

published: 2022-10-12T21:15:09.857

lastModified: 2026-06-17T05:03:00.610

2 source CPE criteria · context only
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:*
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
12 Oct 2022 21:15:09 UTC
Source modified
17 Jun 2026 05:03:00 UTC
Saved here
24 Oct 2026 21:17:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Primary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

osv · GHSA-9mh8-9j64-443f

Published

HashiCorp Vault's revocation list not respected

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.

Source published
6 Jul 2023 19:24:01 UTC
Source modified
10 Sep 2026 03:49:57 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Publisher rating · MODERATE

osv · GO-2023-1897

Published

HashiCorp Vault's revocation list not respected in github.com/hashicorp/vault

HashiCorp Vault's revocation list not respected in github.com/hashicorp/vault

Source published
20 Aug 2024 20:31:35 UTC
Source modified
4 Feb 2026 03:08:09 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 03:46 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current