CVE-2023-0687

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-02-06. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-12716 (ENISA EUVD) · GHSA-5r4p-4pqv-gqhw (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This vulnerability affects the function __monstartup of the file gmon.c of the component Call Graph Monitor. The manipulation leads to buffer overflow. It is recommended to apply a patch to fix this issue. VDB-220246 is the identifier assigned to this vulnerability. NOTE: The real existence of this vulnerability is still doubted at the moment. The inputs that induce this vulnerability are basically addresses of the running application that is built with gmon enabled. It's basically trusted input or input that needs an actual security flaw to be compromised or controlled.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.1%
EPSS %ILE
66th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 6, 2023

Last Modified

October 14, 2026

Advisory Details (3)

Auto-updated Nov 8, 2026
Patch available.
Web pageMentions a patch (unverified)

SSA-398330

https://cert-portal.siemens.com/productcert/html/ssa-398330.html
Web page

29444 – gmon memory corruption due wrong calculation of required buffer size

https://sourceware.org/bugzilla/show_bug.cgi?id=29444
Web page

gmon: Fix allocated buffer overflow (bug 2944) - Patchwork

https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/

Vendor Advisories for CVE-2023-0687(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 73× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 290 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 190 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:43 UTCEPSS rescoreEPSS 1.1% · 66th percentile
  2. 2026-11-13 13:54 UTCEchelonGraph re-scored
  3. 2026-11-13 13:54 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-12 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-12 11:47 UTCEchelonGraph re-scored
  6. 2026-11-12 11:47 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-11 16:33 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-11-11 09:39 UTCEchelonGraph re-scored
  9. 2026-11-11 09:39 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-10 16:36 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-11-10 07:31 UTCEchelonGraph re-scored
  12. 2026-11-10 07:31 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-09 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-11-09 05:23 UTCEchelonGraph re-scored
  15. 2026-11-09 05:23 UTCVendor advisory
  16. 2026-11-09 05:23 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-08 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  18. 2026-11-08 03:16 UTCEchelonGraph re-scored
  19. 2026-11-08 03:16 UTCVendor advisory
  20. 2026-11-08 03:16 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-07 16:34 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  22. 2026-11-07 01:08 UTCEchelonGraph re-scored
  23. 2026-11-07 01:08 UTCVendor advisory
  24. 2026-11-07 01:08 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-11-06 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
Show 75 more
  1. 2026-11-05 22:58 UTCEchelonGraph re-scored
  2. 2026-11-05 22:58 UTCVendor advisory
  3. 2026-11-05 22:58 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-05 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-04 20:51 UTCEchelonGraph re-scored
  6. 2026-11-04 20:51 UTCVendor advisory
  7. 2026-11-04 20:51 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-04 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  9. 2026-11-04 09:25 UTCOSV refresh
  10. 2026-11-03 18:43 UTCEchelonGraph re-scored
  11. 2026-11-03 18:43 UTCVendor advisory
  12. 2026-11-03 18:43 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-03 16:40 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  15. 2026-11-02 16:35 UTCEchelonGraph re-scored
  16. 2026-11-02 16:35 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-11-01 14:08 UTCEchelonGraph re-scored
  18. 2026-11-01 14:08 UTCVendor advisory
  19. 2026-11-01 14:08 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  21. 2026-10-31 11:59 UTCEchelonGraph re-scored
  22. 2026-10-31 11:59 UTCVendor advisory
  23. 2026-10-31 11:59 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  25. 2026-10-30 09:51 UTCEchelonGraph re-scored
  26. 2026-10-30 09:51 UTCVendor advisory
  27. 2026-10-30 09:51 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  29. 2026-10-29 07:44 UTCEchelonGraph re-scored
  30. 2026-10-29 07:44 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  32. 2026-10-28 05:37 UTCEchelonGraph re-scored
  33. 2026-10-28 05:37 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  35. 2026-10-27 03:29 UTCEchelonGraph re-scored
  36. 2026-10-27 03:29 UTCVendor advisory
  37. 2026-10-27 03:29 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  39. 2026-10-25 21:14 UTCVendor advisory
  40. 2026-10-25 21:14 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-25 17:53 UTCEchelonGraph re-scored
  42. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  43. 2026-10-24 19:07 UTCEchelonGraph re-scored
  44. 2026-10-24 19:07 UTCVendor advisory
  45. 2026-10-24 19:07 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  47. 2026-10-23 16:58 UTCEchelonGraph re-scored
  48. 2026-10-23 16:58 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  50. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  51. 2026-10-22 14:51 UTCEchelonGraph re-scored
  52. 2026-10-22 14:51 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  54. 2026-10-21 12:43 UTCEchelonGraph re-scored
  55. 2026-10-21 12:43 UTCVendor advisory
  56. 2026-10-21 12:43 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  58. 2026-10-20 10:35 UTCEchelonGraph re-scored
  59. 2026-10-20 10:35 UTCVendor advisory
  60. 2026-10-20 10:35 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  62. 2026-10-19 08:25 UTCEchelonGraph re-scored
  63. 2026-10-19 08:25 UTCVendor advisory
  64. 2026-10-19 08:25 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  66. 2026-10-18 06:17 UTCEchelonGraph re-scored
  67. 2026-10-18 06:17 UTCVendor advisory
  68. 2026-10-18 06:16 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  70. 2026-10-17 04:08 UTCEchelonGraph re-scored
  71. 2026-10-17 04:08 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  73. 2026-10-16 01:58 UTCEchelonGraph re-scored
  74. 2026-10-16 01:58 UTCGHSA enrichmentGHSA-5r4p-4pqv-gqhw · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.1% · 64th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-0687?
CVE-2023-0687 is a critical-severity vulnerability; its CVE record was published on February 6, 2023. A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This vulnerability affects the function __monstartup of the file gmon.c of the component Call Graph Monitor. The manipulation leads to buffer overflow. It is recommended to apply a patch to fix this issue. VDB-220246…
When was the CVE record for CVE-2023-0687 published?
The CVE record for CVE-2023-0687 was published on February 6, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2023-0687 actively exploited?
CVE-2023-0687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0687?
CVE-2023-0687 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-0687?
A fix for CVE-2023-0687 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0687 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-0687

Explore →

Is Your Infrastructure Affected by CVE-2023-0687?

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

Book a Demo →Browse All CVEs