CVE-2026-42503

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 8.8; sources differ by 0.0.

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

A fix is available — apply it.

gopls by default communicates via pipe. However, -port and -listen flags are supported as means of debugging. If -listen is given a value without an explicit host (e.g. :8080), or -port is used, gopls will listen on 0.0.0.0.  As a result, users might inadvertently cause gopls to bind 0.0.0.0. This can allow a malicious party on the same network to execute code arbitrarily via gopls.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 7, 2026

Advisory Details (2)

Auto-updated May 6, 2026
No patch confirmed yet.
generic

x/tools/gopls: -port and -listen flag makes it easy to bind to 0.0.0.0 and allow RCE · Issue #79211 · golang/go · GitHub

https://go.dev/issue/79211
generic
https://go.dev/cl/774381

Vendor Advisories for CVE-2026-42503(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgolang1-26-main-1.26.2-1.1.hum12026-04-15redhat
redhatgolang1-25-main-1.25.9-1.hum12026-04-10redhat

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gopls2:0.16.1+ds-1, 2:0.21.1+ds-1, 2:0.21.1+ds-2, 2:0.22.0+ds-1, 2:0.22.0+ds-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gopls2:0.16.1+ds-1, 2:0.21.1+ds-1, 2:0.21.1+ds-2, 2:0.22.0+ds-1, 2:0.22.0+ds-2——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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 213 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42503?
CVE-2026-42503 is a high vulnerability published on May 6, 2026. gopls by default communicates via pipe. However, -port and -listen flags are supported as means of debugging. If -listen is given a value without an explicit host (e.g. :8080), or -port is used, gopls will listen on 0.0.0.0. As a result, users might inadvertently cause gopls to bind 0.0.0.0. This…
When was CVE-2026-42503 disclosed?
CVE-2026-42503 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42503 actively exploited?
CVE-2026-42503 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.1% of all scored CVEs.
What is the CVSS score of CVE-2026-42503?
CVE-2026-42503 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-42503?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42503, 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-2026-42503

Explore →

Is Your Infrastructure Affected by CVE-2026-42503?

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

Start Free Scan →Browse All CVEs