How to Fix CVE-2026-5387: Missing authorization in Pipeline Simulation 2025

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

What is CVE-2026-5387?

The vulnerability, if exploited, could allow an unauthenticated miscreant to perform operations intended only for Simulator Instructor or Simulator Developer (Administrator) roles, resulting in privilege escalation with potential for modification of simulation parameters, training configuration, and training records.

Am I affected?

Run the version check that matches your platform:

# Linux
dpkg -s pipeline 2>/dev/null | grep -i version
rpm -q pipeline 2>/dev/null
pipeline --version 2>/dev/null

Compare what you see against the Affected row above (AVEVA Pipeline Simulation 2025 0 to <2025 SP1 (build 7.1.9497.6351)). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-5387

The primary fix is to upgrade Pipeline Simulation 2025 to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: Pipeline Simulation 2025 2025.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade pipeline
pipeline --version 2>/dev/null || dpkg -s pipeline | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --security pipeline -y
rpm -q pipeline

SUSE / openSUSE

sudo zypper patch --category security
rpm -q pipeline

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-5387 affecting Pipeline Simulation 2025
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-5387-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] Detecting installed version of Pipeline Simulation 2025"
    $pkg = winget list --id "Pipeline_Simulation_2025" 2>$null
    Write-Host $pkg

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

    Write-Host "[3/4] Applying upgrade to Pipeline Simulation 2025 2025"
    winget upgrade --id "Pipeline_Simulation_2025" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "Pipeline_Simulation_2025"
    Write-Host "Fix 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-5387 affecting Pipeline Simulation 2025
# Detect -> backup -> upgrade -> verify -> log.

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

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s pipeline 2>/dev/null | grep -i version || echo "pipeline not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q pipeline || echo "pipeline not installed via rpm"
fi

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

echo "[3/4] Applying upgrade (target: Pipeline Simulation 2025 2025)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y pipeline
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y pipeline
elif command -v yum >/dev/null; then
    yum update -y pipeline
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s pipeline 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q pipeline
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)

# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback

# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop pipeline
sudo systemctl disable pipeline

How to verify the fix worked

# Linux
pipeline --version 2>/dev/null || dpkg -s pipeline | grep -i version
rpm -q pipeline 2>/dev/null || true

# Windows
winget list | findstr /I "pipeline"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Pipeline Simulation 2025 2025. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Related fixes

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

• How to Fix CVE-2026-2364: CODESYS Installer TOCTOU Privilege Escalation in CODESYS Installer — CODESYS Installer TOCTOU Privilege Escalation in CODESYS Installer
• How to Fix CVE-2026-21790: Critical Vulnerability in Traveler — Critical Vulnerability in Traveler
• How to Fix CVE-2026-25616: Critical Vulnerability in Blesta , Critical Vulnerability in Blesta
• How to Fix CVE-2026-2798: Use-after-free in Firefox , Use-after-free in Firefox
• How to Fix CVE-2026-23748: Integer underflow in Firmware SDK , Integer underflow in Firmware SDK

Is CVE-2026-5387 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

9.3 (critical). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

• Official vendor advisory: https://www.aveva.com/content/dam/aveva/documents/support/cyber-security-updates/SecurityBulletin_AVEVA-2026-004.pdf
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5387
• https://softwaresupportsp.aveva.com/en-US/downloads/products/details/57b79fdb-7b5f-4125-8a44-833b6b5c6d6f
• https://www.cisa.gov/news-events/ics-advisories/icsa-26-106-04
• https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-106-04.json

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