CVE-2026-27900
Last modified
CVE-2026-27900 is a high-severity vulnerability rated 7.7/10 on the CVSS scale. The Terraform Provider for Linode versions prior to v3.9.0 logged sensitive information including some passwords, StackScript content, and object storage data in debug logs without redaction. Provider debug logging is not enabled by default. EPSS estimates a 0.47% chance of exploitation in the next 30 days.
Description
The Terraform Provider for Linode versions prior to v3.9.0 logged sensitive information including some passwords, StackScript content, and object storage data in debug logs without redaction. Provider debug logging is not enabled by default. This issue is exposed when debug/provider logs are explicitly enabled (for example in local troubleshooting, CI/CD jobs, or centralized log collection). If enabled, sensitive values may be written to logs and then retained, shared, or exported beyond the original execution environment. An authenticated user with access to provider debug logs (through log aggregation systems, CI/CD pipelines, or debug output) would thus be able to extract these sensitive credentials. Versions 3.9.0 and later sanitize debug logs by logging only non-sensitive metadata such as labels, regions, and resource IDs while redacting credentials, tokens, keys, scripts, and other sensitive content. Some other mitigations and workarounds are available. Disable Terraform/provider debug logging or set it to `WARN` level or above, restrict access to existing and historical logs, purge/retention-trim logs that may contain sensitive values, and/or rotate potentially exposed secrets/credentials.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Terraform | Linode Provider | < 3.9.0 |
References
- https://github.com/linode/terraform-provider-linode/pull/2269Issue Tracking, Patch
- http://www.openwall.com/lists/oss-security/2026/02/26/2Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-27900?
How severe is CVE-2026-27900?
How do I fix CVE-2026-27900?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-27895LDAP Account Manager (LAM) is a webfrontend for managing ent…8.8
- CVE-2026-27896The Go MCP SDK used Go's standard encoding/json.Unmarshal fo…7.5
- CVE-2026-27897Vociferous provides cross-platform, offline speech-to-text w…7.1
- CVE-2026-27898Vaultwarden is an unofficial Bitwarden compatible server wri…5.4
- CVE-2026-27899WireGuard Portal (or wg-portal) is a web-based configuration…8.8
- CVE-2026-2790Same-origin policy bypass in the Networking: JAR component. …9.8
- CVE-2026-27901Svelte performance oriented web framework. Prior to version …6.1
- CVE-2026-27902Svelte performance oriented web framework. Prior to version …5.4
- CVE-2026-27903minimatch is a minimal matching utility for converting glob …7.5
- CVE-2026-27904minimatch is a minimal matching utility for converting glob …7.5
- CVE-2026-27905BentoML is a Python library for building online serving syst…7.8
- CVE-2026-27906Improper input validation in Windows Hello allows an authori…4.4
Are you affected by CVE-2026-27900?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
