dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-22565

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 Input Validation vulnerability could allow a malicious actor with access to the UniFi Play network to cause the device to stop responding.
 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 · moderate confidence

Improper input validation in UniFi Play PowerAmp (versions 1.0.35 and earlier) and UniFi Play Audio Port (versions 1.0.24 and earlier) allows a network-adjacent attacker to send specially crafted input that causes the device to become unresponsive, resulting in denial of service.

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 input validation flaw.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 UniFi Play device type
    Determine if the target device is running UniFi Play PowerAmp or UniFi Play Audio Port by checking the device model or firmware information through the UniFi controller or device web interface
    Affected if The device runs either UniFi Play PowerAmp or UniFi Play Audio Port software
  2. Determine installed PowerAmp version
    Access the device settings through the UniFi controller or device web interface and locate the firmware or software version information for UniFi Play PowerAmp
    Affected if The installed version of UniFi Play PowerAmp is 1.0.35 or earlier
  3. Determine installed Audio Port version
    Access the device settings through the UniFi controller or device web interface and locate the firmware or software version information for UniFi Play Audio Port
    Affected if The installed version of UniFi Play Audio Port is 1.0.24 or earlier
  4. Verify network exposure
    Confirm whether the affected device is accessible on the network segment where untrusted attackers could send specially crafted input
    Affected if The device is network-adjacent to untrusted users or systems

A user is affected if their device runs UniFi Play PowerAmp version 1.0.35 or earlier, or UniFi Play Audio Port version 1.0.24 or earlier, and is accessible to network-adjacent attackers.

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 input validation flaw.

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 the affected UniFi Play device(s) on your network (PowerAmp or Audio Port)
  2. 2. Access the UniFi Controller or UniFi Play management interface
  3. 3. Navigate to the device settings for each affected unit
  4. 4. Check the current firmware/software version to confirm it is vulnerable (PowerAmp ≤1.0.35 or Audio Port ≤1.0.24)
  5. 5. For PowerAmp devices: Locate firmware update option and upgrade to version 1.0.38 or later
  6. 6. For Audio Port devices: Locate firmware update option and upgrade to version 1.1.9 or later
  7. 7. Verify the upgrade was successful by confirming the new version numbers
  8. 8. Test device functionality to ensure normal operation

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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