CVE-2024-39689: Certifi removes GLOBALTRUST root certificate
Exploit probability fell from 0.25805 to 0.01049, crossing 0.10. The crossing is the event; the daily drift either side of it is not.
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
- Upgrade to certifi 2024.7.4 or later upper bounds of the CVE record's affected ranges
- 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
- 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 starting in 2021.5.30 and prior to 2024.7.4 recognized root certificates from `GLOBALTRUST`. Certifi 2024.7.04 removes root certificates from `GLOBALTRUST` from the root store. These are in the process of being removed from Mozilla's trust store. `GLOBALTRUST`'s root certificates are being removed pursuant to an investigation which identified "long-running and unresolved compliance issues."
- weakness
- CWE-345: Insufficient Verification of Data Authenticity
- affected
- certifi python-certifi
- published ranges
- certifi >= 2021.5.30 < 2024.7.4; netapp ontap tools 10
- first unaffected version, by branch
- certifi 2024.7.4
- fixed by package (from OSV advisories)
- certifi (PyPI): 2024.7.4 GHSA-248v-346w-9cwc PYSEC-2024-230
- severity
- 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- assigned by
- GitHub_M
- published
- 2024-07-05
check us github.com github.com groups.google.com
Exploit code held, dated
- exploit code
- 1 public proof-of-concept repository, first seen 2024-03-20 (PoC-in-GitHub).
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 6 Jul 2024 | 0.00045 | |
| 13 Feb 2025 | 0.00054 | |
| 17 Mar 2025 | 0.14501 | crossed 0.10 · scoring model v2025.03.14 |
| 20 Mar 2025 | 0.02385 | crossed 0.10 |
| 23 Mar 2025 | 0.17702 | crossed 0.10 |
| 28 Mar 2025 | 0.03034 | crossed 0.10 |
| 29 Mar 2025 | 0.17702 | crossed 0.10 |
| 30 Mar 2025 | 0.03034 | crossed 0.10 |
| 13 Aug 2025 | 0.21233 | crossed 0.10 |
| 18 Nov 2025 | 0.04171 | crossed 0.10 |
| 21 Nov 2025 | 0.21233 | crossed 0.10 |
| 24 May 2026 | 0.25805 | |
| 28 May 2026 | 0.26297 | |
| 10 Jun 2026 | 0.25805 | |
| 15 Jun 2026 | 0.01049 | crossed 0.10 · scoring model v2026.06.15 |
24 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.
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-06-15 (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 2024.7.4. A newer fix from the CNA or OSV changes this brief.
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-2024-39689', '2026-11-01T23:59:59.999999Z', now());