CVE-1999-0199

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(low)
EPSS
82.1%
KEV
Not listed

Published

October 6, 2020

Last Modified

November 20, 2024

Advisory Details (1)

Auto-updated May 30, 2026
Upstream fix merged — awaiting tagged release. 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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 20× 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-07-11 08:22 UTCEPSS rescore
  2. 2026-07-08 15:08 UTCEPSS rescore
  3. 2026-07-04 06:26 UTCEPSS rescore
  4. 2026-07-02 14:00 UTCEPSS rescore
  5. 2026-06-29 14:02 UTCEPSS rescore
  6. 2026-06-28 14:02 UTCEPSS rescore
  7. 2026-06-27 03:04 UTCEPSS rescore
  8. 2026-06-24 14:01 UTCEPSS rescore
  9. 2026-06-24 11:50 UTCOSV refresh
  10. 2026-06-23 21:29 UTCEPSS rescore
  11. 2026-06-22 14:22 UTCEPSS rescore
  12. 2026-06-21 01:56 UTCEPSS rescore
  13. 2026-06-19 19:22 UTCEPSS rescore
  14. 2026-06-18 17:49 UTCEPSS rescore
  15. 2026-06-18 17:49 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-16 17:49 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-13 22:56 UTCEPSS rescore
  20. 2026-06-12 23:07 UTCEPSS rescore
  21. 2026-06-11 13:55 UTCEPSS rescore
  22. 2026-06-10 22:13 UTCEPSS rescore
  23. 2026-06-10 13:17 UTCEPSS rescore
  24. 2026-06-08 14:13 UTCEPSS rescore
  25. 2026-06-07 15:39 UTCOSV refresh
Show 23 more
  1. 2026-06-07 15:21 UTCEPSS rescore
  2. 2026-06-06 13:44 UTCEPSS rescore
  3. 2026-06-05 06:07 UTCEPSS rescore
  4. 2026-06-04 13:09 UTCEPSS rescore
  5. 2026-06-02 20:10 UTCEPSS rescore
  6. 2026-05-31 22:27 UTCEPSS rescore
  7. 2026-05-31 00:13 UTCEPSS rescore
  8. 2026-05-31 00:13 UTCEPSS rescore
  9. 2026-05-29 13:40 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-27 13:37 UTCEPSS rescore
  15. 2026-05-27 13:37 UTCEPSS rescore
  16. 2026-05-26 13:41 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 07:16 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-24 16:42 UTCEPSS rescore
  22. 2026-05-23 07:00 UTCEG score recompute
  23. 2026-05-23 07:00 UTCGHSA enrichment

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 in the National Vulnerability Database on October 6, 2020, with the most recent update on November 20, 2024. 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 82.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-1999-0199?
CVE-1999-0199 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-1999-0199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-1999-0199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs