CVE-2023-3138

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-06-28. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity75% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
75%
KEV
Not listed

Published

June 28, 2023

Last Modified

November 21, 2024

References (10)

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibx11-dev (2:1.8.1-2ubuntu0.2) @ kinetic2026-05-24ubuntu
ubuntulibx11-dev (2:1.6.2-1ubuntu2.1+esm3) @ trusty2026-05-24ubuntu
redhatlibX11-0:1.6.8-6.el8_82024-03-19redhat
redhatlibX11-0:1.7.0-8.el9_22024-03-05redhat
redhatlibX11-0:1.6.8-6.el82023-11-14redhat
redhatlibX11-0:1.7.0-8.el92023-11-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
libx11—1.7.3.1-r1—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
libx11—1.8-r1—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
libx11—1.8.4-r1—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
libx11—1.8.4-r4—
Debian:10(1)
PackageVulnerable rangeFixed inDependents
libx112:1.6.7-1, 2:1.6.7-1+deb10u1, 2:1.6.7-1+deb10u22:1.6.7-1+deb10u3—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libx112:1.7.2-12:1.7.2-1+deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libx112:1.8.4-22:1.8.4-2+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libx11—2:1.8.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libx11—2:1.8.6-1—

Weakness Classification(2)

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

All Vendor Advisories

(7)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-09-07 15:59 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-06 13:45 UTCEPSS rescore
  4. 2026-09-05 15:26 UTCEPSS rescore
  5. 2026-09-04 13:58 UTCEPSS rescore
  6. 2026-09-04 05:04 UTCEPSS rescore
  7. 2026-09-04 02:29 UTCOSV refresh
  8. 2026-09-02 14:09 UTCEPSS rescore
  9. 2026-09-01 13:51 UTCEPSS rescore
  10. 2026-08-30 19:15 UTCEPSS rescore
  11. 2026-08-30 01:20 UTCEPSS rescore
  12. 2026-08-28 21:39 UTCEPSS rescore
  13. 2026-08-27 14:23 UTCEPSS rescore
  14. 2026-08-26 14:44 UTCEPSS rescore
  15. 2026-08-26 14:43 UTCEPSS rescore
  16. 2026-08-25 13:46 UTCEPSS rescore
  17. 2026-08-23 00:17 UTCEPSS rescore
  18. 2026-08-21 23:47 UTCEPSS rescore
  19. 2026-08-20 22:53 UTCEPSS rescore
  20. 2026-08-19 17:02 UTCEPSS rescore
  21. 2026-08-19 17:02 UTCEPSS rescore
  22. 2026-08-18 13:46 UTCEPSS rescore
  23. 2026-08-17 14:23 UTCOSV refresh
  24. 2026-08-17 13:45 UTCEPSS rescore
  25. 2026-08-16 14:54 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 02:12 UTCEPSS rescore
  2. 2026-08-15 01:28 UTCEPSS rescore
  3. 2026-08-15 01:28 UTCEPSS rescore
  4. 2026-08-13 21:58 UTCEPSS rescore
  5. 2026-08-12 13:48 UTCEPSS rescore
  6. 2026-08-11 13:39 UTCEPSS rescore
  7. 2026-08-09 13:44 UTCEPSS rescore
  8. 2026-08-09 13:44 UTCEPSS rescore
  9. 2026-08-08 16:35 UTCEPSS rescore
  10. 2026-08-07 16:25 UTCEPSS rescore
  11. 2026-08-06 13:45 UTCEPSS rescore
  12. 2026-08-05 19:15 UTCEPSS rescore
  13. 2026-08-04 15:07 UTCEPSS rescore
  14. 2026-08-03 10:34 UTCEPSS rescore
  15. 2026-08-03 10:34 UTCEPSS rescore
  16. 2026-08-02 09:28 UTCOSV refresh
  17. 2026-08-02 02:25 UTCEPSS rescore
  18. 2026-08-02 02:25 UTCEPSS rescore
  19. 2026-08-01 04:14 UTCEPSS rescore
  20. 2026-08-01 04:13 UTCEPSS rescore
  21. 2026-07-30 16:26 UTCEPSS rescore
  22. 2026-07-30 16:26 UTCEPSS rescore
  23. 2026-07-30 01:28 UTCEPSS rescore
  24. 2026-07-30 01:28 UTCEPSS rescore
  25. 2026-07-28 15:34 UTCEPSS rescore
  26. 2026-07-28 15:34 UTCEPSS rescore
  27. 2026-07-26 14:52 UTCEPSS rescore
  28. 2026-07-26 14:52 UTCEPSS rescore
  29. 2026-07-25 14:16 UTCEPSS rescore
  30. 2026-07-24 14:16 UTCEPSS rescore
  31. 2026-07-23 14:16 UTCEPSS rescore
  32. 2026-07-23 14:16 UTCEPSS rescore
  33. 2026-07-23 02:22 UTCEG score recompute
  34. 2026-07-22 23:09 UTCEG score recompute
  35. 2026-07-22 14:06 UTCEPSS rescore
  36. 2026-07-21 15:23 UTCEPSS rescore
  37. 2026-07-21 15:23 UTCEPSS rescore
  38. 2026-07-20 17:06 UTCEPSS rescore
  39. 2026-07-19 14:29 UTCEPSS rescore
  40. 2026-07-19 02:27 UTCEPSS rescore
  41. 2026-07-18 10:03 UTCEPSS rescore
  42. 2026-07-18 10:03 UTCEPSS rescore
  43. 2026-07-16 17:01 UTCEPSS rescore
  44. 2026-07-16 17:01 UTCEPSS rescore
  45. 2026-07-15 16:56 UTCEPSS rescore
  46. 2026-07-15 16:56 UTCEPSS rescore
  47. 2026-07-15 16:49 UTCOSV refresh
  48. 2026-07-15 01:58 UTCEPSS rescore
  49. 2026-07-13 22:28 UTCEPSS rescore
  50. 2026-07-13 22:28 UTCEPSS rescore
  51. 2026-07-12 05:45 UTCEPSS rescore
  52. 2026-07-12 05:45 UTCEPSS rescore
  53. 2026-07-11 08:26 UTCEPSS rescore
  54. 2026-07-11 08:26 UTCEPSS rescore
  55. 2026-07-09 19:08 UTCEPSS rescore
  56. 2026-07-08 15:13 UTCEPSS rescore
  57. 2026-07-07 13:44 UTCEPSS rescore
  58. 2026-07-06 16:26 UTCEPSS rescore
  59. 2026-07-06 16:26 UTCEPSS rescore
  60. 2026-07-06 02:22 UTCEPSS rescore
  61. 2026-07-05 02:29 UTCEPSS rescore
  62. 2026-07-04 06:29 UTCEPSS rescore
  63. 2026-07-01 15:05 UTCEPSS rescore
  64. 2026-06-30 23:21 UTCEPSS rescore
  65. 2026-06-30 23:21 UTCEPSS rescore
  66. 2026-06-29 14:05 UTCEPSS rescore
  67. 2026-06-28 14:06 UTCEPSS rescore
  68. 2026-06-28 14:06 UTCEPSS rescore
  69. 2026-06-28 04:55 UTCEPSS rescore
  70. 2026-06-28 04:55 UTCEPSS rescore
  71. 2026-06-27 17:04 UTCOSV refresh
  72. 2026-06-27 03:07 UTCEPSS rescore
  73. 2026-06-27 03:07 UTCEPSS rescore
  74. 2026-06-25 13:48 UTCEPSS rescore
  75. 2026-06-25 13:48 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-3138?
CVE-2023-3138 is a high vulnerability published on June 28, 2023. A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust…
When was CVE-2023-3138 disclosed?
CVE-2023-3138 was first published in the National Vulnerability Database on June 28, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-3138 actively exploited?
CVE-2023-3138 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 25.0% of all scored CVEs.
What is the CVSS score of CVE-2023-3138?
CVE-2023-3138 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-3138?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-3138, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-3138

Explore →

Is Your Infrastructure Affected by CVE-2023-3138?

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

Start Free Scan →Browse All CVEs