CVE-2026-22562
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 · uneditedA malicious actor with access to the UniFi Play network could exploit a Path Traversal vulnerability found in the device firmware to write files on the system that could be used for a remote code execution (RCE). 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 confidenceA path traversal vulnerability in UniFi Play firmware (PowerAmp <=1.0.35, Audio Port <=1.0.24) allows an authenticated attacker on the UniFi Play network to write files to arbitrary system locations, enabling remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if UniFi Play PowerAmp is installedCheck the installed application package or firmware version for PowerAmp on the UniFi Play device. This may be visible in the application UI, system settings, or by querying the device's firmware metadata if accessible.Affected if PowerAmp version is 1.0.35 or lower
-
Identify if UniFi Play Audio Port is installedCheck the installed application package or firmware version for Audio Port on the UniFi Play device. This may be visible in the application UI, system settings, or by querying the device's firmware metadata if accessible.Affected if Audio Port version is 1.0.24 or lower
-
Verify network accessibilityDetermine whether the UniFi Play network interface is exposed to untrusted networks or only accessible to authenticated users within a trusted network segment.Affected if The UniFi Play network interface is accessible to unauthenticated or untrusted users
You are affected if either UniFi Play PowerAmp version is 1.0.35 or lower OR Audio Port version is 1.0.24 or lower AND the device network is accessible to authenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate 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 path traversal vulnerability.
UniFi Play PowerAmp: version 1.0.38 or later; UniFi Play Audio Port: version 1.1.9 or later
- 1. Identify which UniFi Play device(s) are deployed: PowerAmp or Audio Port
- 2. Access the UniFi Play device management interface or controller
- 3. Navigate to the device settings or firmware update section
- 4. Check current firmware version of affected devices
- 5. For UniFi Play PowerAmp devices: Initiate firmware update to version 1.0.38 or later
- 6. For UniFi Play Audio Port devices: Initiate firmware update to version 1.1.9 or later
- 7. Verify successful installation of updated firmware
- 8. Confirm the path traversal vulnerability is remediated by the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22562 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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