dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-22564

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper Access Control vulnerability in UniFi Play PowerAmp (versions 1.0.35 and earlier) and UniFi Play Audio Port (versions 1.0.24 and earlier) allows a malicious actor with access to the UniFi Play network to enable SSH and make unauthorized system changes. This is a critical network-exploitable access control failure with CVSS 9.8.

MitigationUpdate UniFi Play PowerAmp to version 1.0.38 or later and UniFi Play Audio Port to version 1.1.9 or later to remediate the improper access control vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the UniFi Play device model
    Locate the physical UniFi Play device or its network inventory entry - look for 'PowerAmp' or 'Audio Port' labeling in the UniFi controller or on the device itself
    Affected if The device is a UniFi Play PowerAmp or UniFi Play Audio Port unit
  2. Check the installed firmware/software version
    Access the UniFi controller or device web interface and locate the firmware or software version information. Compare against the affected ranges: PowerAmp versions 1.0.35 and earlier, Audio Port versions 1.0.24 and earlier
    Affected if The version number is at or below 1.0.35 for PowerAmp, or at or below 1.0.24 for Audio Port
  3. Verify SSH service status
    Check if SSH is currently enabled on the device - this can be done through the UniFi controller settings, device configuration panel, or by attempting an SSH connection to the device
    Affected if SSH is enabled on the device (the vulnerability allows unauthorized SSH enabling)
  4. Assess network exposure
    Determine if the UniFi Play device is accessible from network segments accessible to untrusted users or if it is on an isolated management VLAN
    Affected if The device is reachable from untrusted network segments without proper network isolation

A user is affected if they have a UniFi Play PowerAmp device on version 1.0.35 or earlier, or a UniFi Play Audio Port on version 1.0.24 or earlier, with SSH enabled or accessible from an untrusted network segment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update UniFi Play PowerAmp to version 1.0.38 or later and UniFi Play Audio Port to version 1.1.9 or later to remediate the improper access control vulnerability.

Recommended fix High confidence

UniFi Play PowerAmp version 1.0.38 or later; UniFi Play Audio Port version 1.1.9 or later

  1. 1. Identify all UniFi Play devices on the network (PowerAmp and Audio Port units)
  2. 2. For each UniFi Play PowerAmp device, check the current firmware version in the UniFi controller or device management interface
  3. 3. For each UniFi Play Audio Port device, check the current firmware version in the UniFi controller or device management interface
  4. 4. For UniFi Play PowerAmp units running version 1.0.35 or earlier, initiate a firmware upgrade to version 1.0.38 or later
  5. 5. For UniFi Play Audio Port units running version 1.0.24 or earlier, initiate a firmware upgrade to version 1.1.9 or later
  6. 6. Verify the upgrade completed successfully by confirming the new firmware versions
  7. 7. After upgrading, verify SSH access controls are functioning as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22564 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22564 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data