Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-66411 is a high-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Coder Coder. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Credentials In Files (T1552.001); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AU-9 (Protection of Audit Information) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-201015
Vulnerability Data
Coder allows organizations to provision remote development environments via Terraform. Prior to 2.26.5, 2.27.7, and 2.28.4, Workspace Agent manifests containing sensitive values were logged in plaintext unsanitized. An attacker with limited local access to the Coder Workspace (VM, K8s Pod…
more
etc.) or a third-party system (SIEM, logging stack) could access those logs. This vulnerability is fixed in 2.26.5, 2.27.7, and 2.28.4.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability (CWE-532) exposes sensitive values including credentials in plaintext logs on local system or logging infrastructure, directly enabling credential access from files.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly protects log files containing sensitive manifest values from unauthorized local or SIEM access.
Enforces secure logging configuration settings that exclude or sanitize sensitive values before they are written.
Requires prompt application of the vendor patches (2.26.5/2.27.7/2.28.4) that stop plaintext logging of sensitive data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.
Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring de-identification and privacy controls before logs leave the organization reduces the chance that sensitive data inadvertently captured in logs becomes exposed to external parties.
By defining what records must be kept, where, and for how long, the control discourages the inadvertent inclusion of sensitive information in logs or other externally accessible files that fall outside the formal record system.
Mandating deletion of temporary files and logs that may contain sensitive information prevents those artifacts from remaining accessible after the data is no longer needed.
When log entries are produced from masked data sets, the control prevents the inadvertent insertion of sensitive values into externally accessible log files.
DLP inspection of logs and file transfers can detect and block the inadvertent placement of sensitive tokens or credentials into externally accessible log files before they are written or transmitted.
Requiring restrictions on free-text fields and proper error-message handling stops developers from embedding or leaking sensitive data into logs or diagnostic output.