How to Fix CVE-2026-27738: Open redirect in angular-cli

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

CVE-2026-27738 is a open redirect in angular angular-cli. The fix is to apply the vendor patch noted below.

What is CVE-2026-27738?

The Angular SSR is a server-rise rendering tool for Angular applications. An Open Redirect vulnerability exists in the internal URL processing logic in versions on the 19.x branch prior to 19.2.21, the 20.x branch prior to 20.3.17, and the 21.x branch prior to 21.1.5 and 21.2.0-rc.1. The logic normalizes URL segments by stripping leading slashes; however, it only removes a single leading slash. When an Angular SSR application is deployed behind a proxy that passes the X-Forwarded-Prefix header, an attacker can provide a value starting with three slashes. This vulnerability allows attackers to conduct large-scale phishing and SEO hijacking. to be vulnerable, the application must use Angular SSR, the application must have routes that perform internal redirects, the infrastructure (Reverse Proxy/CDN) must pass the X-Forwarded-Prefix header to the SSR process without sanitization, and the cache must not vary on the X-Forwarded-Prefix header. Versions 21.2.0-rc.1, 21.1.5, 20.3.17, and 19.2.21 contain a patch. Until the patch is applied, developers should sanitize the X-Forwarded-Prefix header in theirserver.ts before the Angular engine processes the request. The CVSS base score is 6.9 (Medium). The official advisory is at https://github.com/angular/angular-cli/security/advisories/GHSA-xh43-g2fq-wjrj.

Am I affected?

Check the version of angular-cli you are running and compare it against the Affected row above (angular-cli >= 21.2.0-next.2, < 21.2.0-rc.0; angular-cli >= 21.0.0-next.0, < 21.1.5; angular-cli >= 20.0.0-next.0, < 20.3.17; angular-cli >= 19.0.0-next.0, < 19.2.21). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

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

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

How to fix CVE-2026-27738

Upgrade angular-cli 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 angular-cli
dpkg -s angular-cli | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

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

SUSE / openSUSE

sudo zypper refresh
sudo zypper update angular-cli
rpm -q angular-cli

Node.js / npm

# Update the affected package in your project
npm install angular-cli@latest
npm ls angular-cli
npm audit fix

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-27738 affecting angular-cli
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

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

Disable the affected service (Linux)

sudo systemctl stop angular-cli 2>/dev/null || true
sudo systemctl disable angular-cli 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 angular-cli 2>/dev/null | grep -i ^Version
rpm -q angular-cli 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 "*angular-cli*" | 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-25532: Critical Vulnerability in esp-idf — Critical Vulnerability in esp-idf
• How to Fix CVE-2026-20750: Access Control Bypass in Gitea Open Source Git Server — Access Control Bypass in Gitea Open Source Git Server
• How to Fix CVE-2026-7202: OS Command Injection in A8000RU , OS Command Injection in A8000RU
• How to Fix CVE-2026-21011: Cwe-266: incorrect privilege assignment in Samsung Mobile Devices , Cwe-266: incorrect privilege assignment in Samsung Mobile Devices
• How to Fix CVE-2026-32710: Path Traversal in server , Path Traversal in server

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

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

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

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

The vendor advisory is at https://github.com/angular/angular-cli/security/advisories/GHSA-xh43-g2fq-wjrj. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27738.

References

• Official vendor advisory: https://github.com/angular/angular-cli/security/advisories/GHSA-xh43-g2fq-wjrj
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27738
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://github.com/angular/angular-cli/issues/32501
• Additional reference: https://github.com/angular/angular-cli/pull/32521
• Additional reference: https://github.com/angular/angular-cli/commit/877f017ace4b83277d773aa37f5813e5e9faec7e

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