How severe is CVE-2026-27900?

CVE-2026-27900 has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-27900?

CVE-2026-27900 affects the following packages: github.com/linode/terraform-provider-linode/v3 (Go), github.com/linode/terraform-provider-linode/v2 (Go), github.com/linode/terraform-provider-linode (Go). Ecosystems affected: Go.

How do I fix CVE-2026-27900?

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.

How do I detect CVE-2026-27900 in my Go dependencies?

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.

How do I mitigate CVE-2026-27900 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-27900 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27900 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27900?

CVE-2026-27900 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27900?

CVE-2026-27900 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27900 published, and has it been updated?

CVE-2026-27900 was published on February 26, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2026-27900 — terraform-provider-linode

MEDIUMFix: linode/terraform-provider-linode@43a925d

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

Also known asGHSA-5rc7-2jj6-mp64GO-2026-4562

Published

Feb 26, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹github.com/linode/terraform-provider-linode/v3🐹github.com/linode/terraform-provider-linode/v2🐹github.com/linode/terraform-provider-linode

Real-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 WARN level or above
- To disable the logging, you can unset TF_LOG_PROVIDER and TF_LOG environment variables
- Or you can set them to WARN or ERROR levels to avoid sensitive information logged in INFO and DEBUG levels.
- See Terraform docs for details: https://developer.hashicorp.com/terraform/internals/debugging
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

3 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/linode/terraform-provider-linode/v3`	all versions	3.9.0`go 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

Affected Products

1 product · 1 configurations

Application

linode providerterraform

< 3.9.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

### 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: