← console
voxell vciy

CVE-2022-23491: Removal of TrustCor root certificate

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to certifi 2022.12.7 or later upper bounds of the CVE record's affected ranges
  2. Later advisories still cover the fixes above and name higher ones: certifi 2023.7.22 (CVE-2023-37920), 2024.7.4 (CVE-2024-39689) OSV advisories
  3. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  4. Check your version against the ranges this record publishes.

What it is stated by the CNA

Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.

weakness
CWE-345: Insufficient Verification of Data Authenticity
affected
certifi python-certifi
published ranges
certifi >= 2017.11.5 < 2022.12.7
first unaffected version, by branch
certifi 2022.12.7
fixed by package (from OSV advisories)
certifi (PyPI): 2022.12.07; 2022.12.7 GHSA-43fp-rhv2-5gv8 PYSEC-2022-42986
later fixes (from OSV advisories)
certifi 2022.12.07 is inside a range CVE-2023-37920 (GHSA-xqr8-7jwr-rhp7) lists as affected. That advisory is fixed in 2023.7.22.certifi 2022.12.07 is inside a range CVE-2024-39689 (GHSA-248v-346w-9cwc) lists as affected. That advisory is fixed in 2024.7.4.certifi 2022.12.7 is inside a range CVE-2023-37920 (GHSA-xqr8-7jwr-rhp7) lists as affected. That advisory is fixed in 2023.7.22.certifi 2022.12.7 is inside a range CVE-2024-39689 (GHSA-248v-346w-9cwc) lists as affected. That advisory is fixed in 2024.7.4.
severity
6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
assigned by
GitHub_M
published
2022-12-07

check us github.com groups.google.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
8 Dec 20220.00885
7 Mar 20230.00047scoring model v2023.03.01
8 Mar 20230.00047
16 Mar 20230.00055
17 Mar 20250.00039scoring model v2025.03.14
15 Jun 20260.00535scoring model v2026.06.15
17 Sep 20260.0056
28 Sep 20260.00511
7 Oct 20260.0053

36 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-10-07 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: certifi 2022.12.7. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2022-23491', '2026-10-30T23:59:59.999999Z', now());