dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-22566

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 obtain UniFi Play WiFi credentials.
 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

An 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 obtain WiFi credentials due to insufficient access restrictions on credential storage or transmission.

MitigationUpdate UniFi Play PowerAmp to version 1.0.38 or later and UniFi Play Audio Port to version 1.1.9 or later. Restrict network access to trusted personnel until patches are applied.

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
None
Availability
None

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

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 product
    Determine which UniFi Play device or software is deployed: UniFi Play PowerAmp or UniFi Play Audio Port. Check the product model, firmware information, or application listing.
    Affected if The device runs UniFi Play PowerAmp or UniFi Play Audio Port software.
  2. Check the installed version of PowerAmp
    Locate the version information for UniFi Play PowerAmp in the device management interface, firmware release notes, or system information panel. Note the exact version number.
    Affected if The installed version is 1.0.35 or any earlier version.
  3. Check the installed version of Audio Port
    Locate the version information for UniFi Play Audio Port in the device management interface, firmware release notes, or system information panel. Note the exact version number.
    Affected if The installed version is 1.0.24 or any earlier version.
  4. Assess network exposure
    Review network configuration to determine if the UniFi Play device is accessible from untrusted network segments. Check firewall rules, VLAN assignments, and access control lists that govern who can reach the device.
    Affected if The device is reachable from network segments that include untrusted or unauthorized users.

A user is affected if the installed UniFi Play PowerAmp is version 1.0.35 or earlier, or UniFi Play Audio Port is version 1.0.24 or earlier, AND the device is accessible from an untrusted network segment where a malicious actor could attempt credential retrieval.

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. Restrict network access to trusted personnel until patches are applied.

Recommended fix High confidence

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

  1. Identify the UniFi Play device model (PowerAmp or Audio Port)
  2. Check the current installed firmware/software version on the device
  3. Download the latest firmware from the official Ubiquiti Downloads page or through the UniFi Play application
  4. For UniFi Play PowerAmp: Update to version 1.0.38 or later
  5. For UniFi Play Audio Port: Update to version 1.1.9 or later
  6. Verify the update was successful and confirm the new version is running
  7. Test that WiFi credentials are no longer exposed through the vulnerability

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22566 — 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-22566 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