CVE-2025-66411: GO-2025-4182 - Coder logs sensitive objects unsanitized in github.com/coder/coder

CVE-2025-66411 · Severity: low · CVSS 3.1 · Published 2025-12-08

Coder logs sensitive objects unsanitized in github.com/coder/coder

Technologies: github.com/coder/coder (Go), github.com/coder/coder/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2025-66411 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-66411 being exploited in the wild.
How severe is CVE-2025-66411?
Low severity, with a CVSS score of 3.1, published 8 December 2025.
Which products and versions are affected?
github.com/coder/coder (Go) SEMVER:introduced=0; github.com/coder/coder/v2 (Go) SEMVER:introduced=0,fixed=2.26.5, SEMVER:introduced=0,fixed=2.26.5,introduced=2.27.0,fixed=2.27.7,introduced=2.28.0,fixed=2.28.4.
Is there a fix for CVE-2025-66411?
Yes. github.com/coder/coder/v2 (Go): upgrade to 2.26.5, 2.28.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-66411?
Check whether you run github.com/coder/coder (Go) or github.com/coder/coder/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/coder/coder/v2 (Go): upgrade to 2.26.5, 2.28.4 or later
    go get github.com/coder/coder/v2@v2.28.4

Affected products

  • github.com/coder/coder (Go) SEMVER:introduced=0
  • github.com/coder/coder/v2 (Go) SEMVER:introduced=0,fixed=2.26.5, SEMVER:introduced=0,fixed=2.26.5,introduced=2.27.0,fixed=2.27.7,introduced=2.28.0,fixed=2.28.4

Identifiers

  • CVE-2025-66411
  • GHSA-jf75-p25m-pw74
  • GO-2025-4182

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.