How to Fix CVE-2026-22564: Access control - generic in UniFi Play Audio Port
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 9.8 (Critical) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Ubiquiti Inc UniFi Play PowerAmp 0 to <1.0.38; Ubiquiti Inc UniFi Play Audio Port 0 to <1.1.9 |
| Fixed in | UniFi Play PowerAmp 1.0.38; UniFi Play Audio Port 1.1.9 |
| Type (CWE) | CWE-284: Improper Access Control - Generic |
What is CVE-2026-22564?
An Improper Access Control vulnerability could allow a malicious actor with access to the UniFi Play network to enable SSH to make unauthorized changes to the system. Affected Products: UniFi Play PowerAmp (Version 1.0.35 and earlier) UniFi Play Audio Port (Version 1.0.24 and earlier) Mitigation: Update UniFi Play PowerAmp to Version 1.0.38 or later Update UniFi Play Audio Port to Version 1.1.9 or later
Am I affected?
From the device CLI, run the version check:
# Cisco IOS/IOS XE
show version | include Version
# FortiGate (FortiOS)
get system status
# Palo Alto (PAN-OS)
show system info | match sw-version
# Juniper (Junos)
show version
Compare what you see against the Affected row above (Ubiquiti Inc UniFi Play PowerAmp 0 to <1.0.38; Ubiquiti Inc UniFi Play Audio Port 0 to <1.1.9). If your build sits inside that range, the device is exposed and should be upgraded.
How to fix CVE-2026-22564
The primary fix is to upgrade UniFi Play Audio Port to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: UniFi Play PowerAmp 1.0.38; UniFi Play Audio Port 1.1.9.
Network appliance CLI
Connect via SSH or console, then apply the patched firmware following the vendor's standard image upload + reboot procedure for UniFi Play Audio Port.
Complete operator runbook (network appliance)
Run this from your management workstation (Linux/macOS or Windows with a TFTP server reachable). It shells into the device, backs up the running config, transfers the patched image, and reloads.
# Vendor advisory: https://community.ui.com/releases/Security-Advisory-Bulletin-063/e468dd4b-5090-4ef8-89d8-939903c08e83
#!/usr/bin/env bash
# CVE-2026-22564 fix runbook for Ubiquiti Inc UniFi Play Audio Port
# Target build: UniFi Play PowerAmp 1.0.38; UniFi Play Audio Port 1.1.9
set -euo pipefail
DEVICE="${1:?usage: $0 <device-ip> <patched-image-file> <tftp-server-ip>}"
IMAGE="${2:?patched image filename required}"
TFTP="${3:?tftp server ip required}"
LOG="/var/log/cve-2026-22564-$(date +%Y%m%d-%H%M%S).log"
echo "[1/4] Pulling current config from $DEVICE"
ssh admin@"$DEVICE" "show version" | tee -a "$LOG"
ssh admin@"$DEVICE" "copy running-config tftp://$TFTP/cve-2026-22564-pre.cfg"
echo "[2/4] Uploading patched image $IMAGE via TFTP"
ssh admin@"$DEVICE" "copy tftp://$TFTP/$IMAGE flash:$IMAGE" | tee -a "$LOG"
echo "[3/4] Setting boot image and reloading"
ssh admin@"$DEVICE" "configure terminal
boot system flash:$IMAGE
end
write memory
reload" | tee -a "$LOG"
echo "[4/4] Wait ~5 minutes, then verify"
sleep 300
ssh admin@"$DEVICE" "show version | include Version" | tee -a "$LOG"
echo "Compare reported version against UniFi Play PowerAmp 1.0.38; UniFi Play Audio Port 1.1.9"
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 appliance ACL
# Cisco IOS example: restrict management plane to a trusted subnet
configure terminal
access-list 99 permit 10.0.0.0 0.255.255.255
line vty 0 15
access-class 99 in
end
write memory
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop unifi
sudo systemctl disable unifi
How to verify the fix worked
# Linux
unifi --version 2>/dev/null || dpkg -s unifi | grep -i version
rpm -q unifi 2>/dev/null || true
# Windows
winget list | findstr /I "unifi"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above UniFi Play PowerAmp 1.0.38; UniFi Play Audio Port 1.1.9. 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-30579: Critical Vulnerability in n/a — Critical Vulnerability in n/a
- How to Fix CVE-2026-32758: CWE-863: Incorrect Authorization in filebrowser — CWE-863: Incorrect Authorization in filebrowser
- How to Fix CVE-2026-21492: Path Traversal in iccDEV , Path Traversal in iccDEV
- How to Fix CVE-2026-35595: Improper privilege management in vikunja , Improper privilege management in vikunja
- How to Fix CVE-2026-8773: Critical Vulnerability in litemall , Critical Vulnerability in litemall
Is CVE-2026-22564 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.8 (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://community.ui.com/releases/Security-Advisory-Bulletin-063/e468dd4b-5090-4ef8-89d8-939903c08e83
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22564
*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.*