⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5

How to Fix CVE-2026-27900: Log exposure of sensitive info in terraform-provider-linode

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27900 is a log exposure of sensitive info in linode terraform-provider-linode. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity5 (Medium)
Actively exploited?No public listing in CISA KEV
Affectedterraform-provider-linode < 3.9.0
Fixed inSee vendor advisory
Type (CWE)CWE-532: Insertion of Sensitive Information into Log File

What is CVE-2026-27900?

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. The CVSS base score is 5 (Medium). The official advisory is at https://github.com/linode/terraform-provider-linode/security/advisories/GHSA-5rc7-2jj6-mp64.

Am I affected?

Check the version of terraform-provider-linode you are running and compare it against the Affected row above (terraform-provider-linode < 3.9.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s terraform-provider-linode 2>/dev/null | grep -i ^Version
rpm -q terraform-provider-linode 2>/dev/null
command -v terraform-provider-linode >/dev/null && terraform-provider-linode --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*terraform-provider-linode*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "terraform-provider-linode" 2>$null

How to fix CVE-2026-27900

Upgrade terraform-provider-linode to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade terraform-provider-linode
dpkg -s terraform-provider-linode | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh terraform-provider-linode -y
# or for older releases:
sudo yum update terraform-provider-linode -y
rpm -q terraform-provider-linode

SUSE / openSUSE


sudo zypper refresh
sudo zypper update terraform-provider-linode
rpm -q terraform-provider-linode

Node.js / npm


# Update the affected package in your project
npm install terraform-provider-linode@latest
npm ls terraform-provider-linode
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27900 affecting terraform-provider-linode
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27900-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*terraform-provider-linode*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\terraform-provider-linode-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\terraform-provider-linode" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "terraform-provider-linode" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "terraform-provider-linode"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27900 affecting terraform-provider-linode
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27900-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s terraform-provider-linode 2>/dev/null | grep -i ^Version || echo "terraform-provider-linode not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q terraform-provider-linode || echo "terraform-provider-linode not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27900-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/terraform-provider-linode /etc/terraform-provider-linode.d /etc/terraform-provider-linode.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y terraform-provider-linode
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y terraform-provider-linode
elif command -v yum >/dev/null; then
    yum update -y terraform-provider-linode
elif command -v zypper >/dev/null; then
    zypper --non-interactive update terraform-provider-linode
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s terraform-provider-linode 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q terraform-provider-linode
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27900" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27900"

Disable the affected service (Linux)


sudo systemctl stop terraform-provider-linode 2>/dev/null || true
sudo systemctl disable terraform-provider-linode 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s terraform-provider-linode 2>/dev/null | grep -i ^Version
rpm -q terraform-provider-linode 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*terraform-provider-linode*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-27900 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27900?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

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

5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N.

Where is the official advisory for CVE-2026-27900?

The vendor advisory is at https://github.com/linode/terraform-provider-linode/security/advisories/GHSA-5rc7-2jj6-mp64. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27900.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*