How to Fix CVE-2026-3236: Incorrect authorization in Octopus Server

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

CVE-2026-3236 is a incorrect authorization in Octopus Deploy Octopus Server. The fix is to apply the vendor patch noted below.

What is CVE-2026-3236?

In affected versions of Octopus Server it was possible to create a new API key from an existing access token resulting in the new API key having a lifetime exceeding the original API key used to mint the access token. The CVSS base score is 2.3 (Low). The official advisory is at https://advisories.octopus.com/post/2026/sa2026-02.

Am I affected?

Check the version of Octopus Server you are running and compare it against the Affected row above (Octopus Server 2023.0.0 to <2025.3.14761; Octopus Server 2025.4.0 to <2025.4.10409). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

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

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

How to fix CVE-2026-3236

Upgrade Octopus Server 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 octopus-server
dpkg -s octopus-server | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh octopus-server -y
# or for older releases:
sudo yum update octopus-server -y
rpm -q octopus-server

SUSE / openSUSE

sudo zypper refresh
sudo zypper update octopus-server
rpm -q octopus-server

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-3236 affecting Octopus Server
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-3236-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 "*Octopus Server*" -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\octopus-server-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Octopus Server" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Octopus Server" --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 "Octopus Server"
    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-3236 affecting Octopus Server
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-3236-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 octopus-server 2>/dev/null | grep -i ^Version || echo "octopus-server not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q octopus-server || echo "octopus-server not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3236-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/octopus-server /etc/octopus-server.d /etc/octopus-server.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 octopus-server
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y octopus-server
elif command -v yum >/dev/null; then
    yum update -y octopus-server
elif command -v zypper >/dev/null; then
    zypper --non-interactive update octopus-server
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s octopus-server 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q octopus-server
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-3236" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3236"

Disable the affected service (Linux)

sudo systemctl stop octopus-server 2>/dev/null || true
sudo systemctl disable octopus-server 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 octopus-server 2>/dev/null | grep -i ^Version
rpm -q octopus-server 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 "*Octopus Server*" | 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

Related fixes

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

• How to Fix CVE-2026-43504: CWE-863 Incorrect Authorization in Prosody — CWE-863 Incorrect Authorization in Prosody
• How to Fix CVE-2026-4438: gethostbyaddr and gethostbyaddr_r return invalid DNS hostnames in glibc — gethostbyaddr and gethostbyaddr_r return invalid DNS hostnames in glibc
• How to Fix CVE-2026-0692: Critical Vulnerability in BlueSnap Payment Gateway for WooCommerce , Critical Vulnerability in BlueSnap Payment Gateway for WooCommerce
• How to Fix CVE-2026-34607: emlog (Bundle Sibling) , emlog (Bundle Sibling)
• How to Fix CVE-2026-44925: Critical Vulnerability in n/a , Critical Vulnerability in n/a

Is CVE-2026-3236 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-3236?

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-3236?

2.3 (Low). Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N.

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

The vendor advisory is at https://advisories.octopus.com/post/2026/sa2026-02. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3236.

References

• Official vendor advisory: https://advisories.octopus.com/post/2026/sa2026-02
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3236
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

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