dbcve.org
Unifi ProtectApplication · Ui

CVE-2026-54407

HIGH · 8.6 CVSS v3.1 Published 2026-07-02
Fix available
A fix is available. Upgrade to 7.1.83 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
A malicious actor with access to the network could exploit an Improper Access Control vulnerability found in UniFi Protect Application to bypass authentication in certain UniFi Protect Application API endpoints.

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

This Improper Access Control vulnerability in UniFi Protect Application allows a malicious actor with network access to bypass authentication on certain API endpoints, potentially granting unauthorized access to the protection system.

MitigationApply vendor patches from Ubiquiti when available and implement network access controls to limit exposure until the update can be deployed.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Unifi ProtectApplication
Affected:< 7.1.83

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Check UniFi Protect version
    Access the UniFi Protect controller or console and navigate to the system settings or about section to view the installed application version number
    Affected if The displayed version is lower than 7.1.83 (for example, 7.1.82, 7.0.x, or earlier)
  2. Verify network exposure of Protect API
    Review network configuration to determine if the UniFi Protect application management interface is accessible from untrusted networks or the internet
    Affected if The Protect API ports (typically 443 or 8080 for the controller) are exposed to networks outside the trusted local network
  3. Confirm remote access is enabled
    Check the UniFi Protect settings for remote access or cloud access features that allow API connections from external locations
    Affected if Remote access or cloud link features are enabled and accessible from outside the local network

A user is affected if their UniFi Protect version is below 7.1.83 AND the management interface or API endpoints are reachable from untrusted network segments.

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
Upgrade available Upgrade to 7.1.83 or later
Fixed in 7.1.83
Interim mitigation

Apply vendor patches from Ubiquiti when available and implement network access controls to limit exposure until the update can be deployed.

Recommended fix Moderate confidence

UniFi Protect 7.1.83 or later

  1. 1. Access the UniFi OS Console hosting UniFi Protect (e.g., UniFi Dream Machine, UniFi Security Gateway, or UniFi Cloud Key).
  2. 2. Navigate to the UniFi Protect application settings within the UniFi OS interface.
  3. 3. Check the current version of UniFi Protect to confirm it is below 7.1.83.
  4. 4. Initiate the update through the UniFi OS interface (Settings > System > Software > Check for Update) or use the UniFi Controller if applicable.
  5. 5. Alternatively, if using UniFi Cloud Key or Dream Machine, access the device directly and check for available firmware/software updates.
  6. 6. Apply the update to UniFi Protect version 7.1.83 or later.
  7. 7. After the update completes, verify the new version by checking the UniFi Protect application information.
  8. 8. Confirm the authentication bypass vulnerability is resolved by testing access to the previously affected API endpoints.
Caveat Minor release upgrade; review UniFi Protect 7.1.x release notes for any configuration or feature changes before proceeding

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

Fix this in Unifi Protect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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