CVE-2026-27900 is a medium-severity (CVSS 5) CWE-532 vulnerability in github.com/linode/terraform-provider-linode/v3. A fix is available for github.com/linode/terraform-provider-linode/v3 — see the affected versions and patch details below.
Terraform Provider Debug Logs Vulnerable to Sensitive Information Exposure
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27900.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-27900 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/linode/terraform-provider-linode/v3🐹github.com/linode/terraform-provider-linode/v2🐹github.com/linode/terraform-provider-linodeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The Terraform Provider for Linode versions prior to v3.9.0 logged sensitive information including some passwords, StackScript content, object storage data, and NodeBalancer TLS keys in debug logs without redaction.
Important: 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.
Specifically:
- Instance creation operations logged the full InstanceCreateOptions struct containing RootPass and StackScriptData
- Instance disk creation logged InstanceDiskCreateOptions containing RootPass and StackscriptData
- StackScript update operations logged the complete script content via StackscriptUpdateOptions.Script
- Image share group member creation logged tokens in ImageShareGroupAddMemberOptions.Token
- Object storage operations logged full PutObjectInput structures containing user data
- NodeBalancer config create and update operations logged NodeBalancerConfigCreateOptions and NodeBalancerConfigUpdateOptions containing the SSLKey (TLS private key)
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.
Patches
Update to version v3.9.0 or later, which sanitizes 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.
Workarounds and Mitigations
- Disable Terraform/provider debug logging or set it to
WARNlevel or above- To disable the logging, you can unset
TF_LOG_PROVIDERandTF_LOGenvironment variables - Or you can set them to
WARNorERRORlevels to avoid sensitive information logged inINFOandDEBUGlevels. - See Terraform docs for details: https://developer.hashicorp.com/terraform/internals/debugging
- To disable the logging, you can unset
- Restrict access to existing and historical logs
- Purge/retention-trim logs that may contain sensitive values
- Rotate potentially exposed secrets/credentials, including:
- Root passwords
- Image share group tokens
- TLS private keys/certificates used in NodeBalancer configs
- StackScript content/secrets if embedded
Credits
This issue was reported to Terraform by Hasan Sheet via Akamai's HackerOne Bug Bounty program.
Resources
https://github.com/linode/terraform-provider-linode/releases/tag/v3.9.0 https://github.com/linode/terraform-provider-linode/pull/2269 https://github.com/linode/terraform-provider-linode/commit/43a925d826b999f0355de3dc7330c55f496824c0
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/linode/terraform-provider-linode/v3 | all versions | 3.9.0go get github.com/linode/terraform-provider-linode/v3@v3.9.0 |
| 🐹Go | github.com/linode/terraform-provider-linode/v2 | all versions | No fix |
| 🐹Go | github.com/linode/terraform-provider-linode | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/linode/terraform-provider-linode/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/linode/terraform-provider-linode/v3 to 3.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27900 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27900 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-27900. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-27900 in your dependencies?
O3 Security finds CVE-2026-27900 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.