gopls by default communicates via pipe.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. May 6, 2026 · NIST NVD

   Detected

   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.

2. Sep 18, 2026 · NIST NVD

   Updated

   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.

Affected

• cpe golang/goplsversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-42503

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-42503

  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

  nvd.nist.gov

References

• Patch · go.dev
• Issue Tracking · go.dev