CVE-1999-0199

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.4% (83rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement about the unspecified tdelete return value upon deletion of a tree's root, which might allow attackers to access a dangling pointer in an application whose developer was unaware of a documentation update from 1999.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.4%
EPSS %ILE
83rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 6, 2020

Last Modified

September 25, 2026

Advisory Details (2)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit.
github_commit

commit 2864e7670533 (bminor/glibc)

Fix landed in bminor/glibc commit 2864e7670533 — awaiting tagged release

https://github.com/bminor/glibc/commit/2864e767053317538feafa815046fff89e5a16be#diff-94e8c502f255fdfc346df0e29fd4ef40
generic
https://ftp.gnu.org/gnu/glibc/glibc-2.2.tar.gz

Vendor Advisories for CVE-1999-0199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
glibc—
  • every version up to 2.2-1: fixed in 2.2-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
glibc—
  • every version up to 2.2-1: fixed in 2.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
glibc—
  • every version up to 2.2-1: fixed in 2.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
glibc—
  • every version up to 2.2-1: fixed in 2.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 19:58 UTCEPSS rescore
  2. 2026-10-08 16:26 UTCEPSS rescore
  3. 2026-10-07 23:35 UTCEPSS rescore
  4. 2026-10-06 15:07 UTCEPSS rescore
  5. 2026-10-05 17:36 UTCEPSS rescore
  6. 2026-10-04 23:14 UTCEPSS rescore
  7. 2026-09-29 02:28 UTCEG score recompute
  8. 2026-09-25 20:20 UTCEG score recompute
  9. 2026-09-25 20:20 UTCGHSA enrichment
  10. 2026-09-20 01:16 UTCOSV refresh
  11. 2026-09-04 04:59 UTCEPSS rescore
  12. 2026-09-01 04:59 UTCOSV refresh
  13. 2026-08-15 04:37 UTCOSV refresh
  14. 2026-08-03 10:27 UTCEPSS rescore
  15. 2026-07-30 16:51 UTCOSV refresh
  16. 2026-07-23 00:40 UTCEG score recompute
  17. 2026-07-23 00:23 UTCEG score recompute
  18. 2026-07-22 23:45 UTCEG score recompute
  19. 2026-07-22 21:24 UTCEG score recompute
  20. 2026-07-20 17:02 UTCEPSS rescore
  21. 2026-07-18 09:59 UTCEPSS rescore
  22. 2026-07-16 16:58 UTCEPSS rescore
  23. 2026-07-15 16:53 UTCEPSS rescore
  24. 2026-07-15 01:55 UTCEPSS rescore
  25. 2026-07-13 06:07 UTCEPSS rescore
Show 49 more
  1. 2026-07-13 02:07 UTCOSV refresh
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-08 15:08 UTCEPSS rescore
  4. 2026-07-04 06:26 UTCEPSS rescore
  5. 2026-07-02 14:00 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-28 14:02 UTCEPSS rescore
  8. 2026-06-27 03:04 UTCEPSS rescore
  9. 2026-06-24 14:01 UTCEPSS rescore
  10. 2026-06-24 11:50 UTCOSV refresh
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-22 14:22 UTCEPSS rescore
  13. 2026-06-21 01:56 UTCEPSS rescore
  14. 2026-06-19 19:22 UTCEPSS rescore
  15. 2026-06-18 17:49 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-17 17:49 UTCEPSS rescore
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-14 23:13 UTCEPSS rescore
  20. 2026-06-13 22:56 UTCEPSS rescore
  21. 2026-06-12 23:07 UTCEPSS rescore
  22. 2026-06-11 13:55 UTCEPSS rescore
  23. 2026-06-10 22:13 UTCEPSS rescore
  24. 2026-06-10 13:17 UTCEPSS rescore
  25. 2026-06-08 14:13 UTCEPSS rescore
  26. 2026-06-07 15:39 UTCOSV refresh
  27. 2026-06-07 15:21 UTCEPSS rescore
  28. 2026-06-06 13:44 UTCEPSS rescore
  29. 2026-06-05 06:07 UTCEPSS rescore
  30. 2026-06-04 13:09 UTCEPSS rescore
  31. 2026-06-02 20:10 UTCEPSS rescore
  32. 2026-05-31 22:27 UTCEPSS rescore
  33. 2026-05-31 00:13 UTCEPSS rescore
  34. 2026-05-31 00:13 UTCEPSS rescore
  35. 2026-05-29 13:40 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-28 13:42 UTCEPSS rescore
  39. 2026-05-28 13:42 UTCEPSS rescore
  40. 2026-05-27 13:37 UTCEPSS rescore
  41. 2026-05-27 13:37 UTCEPSS rescore
  42. 2026-05-26 13:41 UTCEPSS rescore
  43. 2026-05-26 13:41 UTCEPSS rescore
  44. 2026-05-26 13:41 UTCEPSS rescore
  45. 2026-05-26 07:16 UTCEPSS rescore
  46. 2026-05-26 07:16 UTCEPSS rescore
  47. 2026-05-24 16:42 UTCEPSS rescore
  48. 2026-05-23 07:00 UTCEG score recompute
  49. 2026-05-23 07:00 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-1999-0199?
CVE-1999-0199 is a critical vulnerability published on October 6, 2020. manual/search.texi in the GNU C Library (aka glibc) before 2.2 lacks a statement about the unspecified tdelete return value upon deletion of a tree's root, which might allow attackers to access a dangling pointer in an application whose developer was unaware of a documentation update from 1999.
When was CVE-1999-0199 disclosed?
CVE-1999-0199 was first published on October 6, 2020, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-1999-0199 actively exploited?
CVE-1999-0199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-1999-0199?
CVE-1999-0199 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-1999-0199?
A fix for CVE-1999-0199 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-1999-0199 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-1999-0199

Explore →

Is Your Infrastructure Affected by CVE-1999-0199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs