CVE-2025-23116
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 · uneditedAn Authentication Bypass vulnerability on UniFi Protect Application with Auto-Adopt Bridge Devices enabled could allow a malicious actor with access to UniFi Protect Cameras adjacent network to take control of UniFi Protect Cameras.
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 confidenceThis is an authentication bypass vulnerability in UniFi Protect that allows an attacker on the same network segment as UniFi Protect Cameras to bypass authentication and gain full control of the cameras, specifically when the Auto-Adopt Bridge Devices feature is enabled.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/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.
-
Locate UniFi Protect installationIdentify the UniFi Protect controller or application in your environment. Check for UniFi Dream Machine, UniFi Cloud Key, or dedicated UniFi Protect server installations. Look for the 'protect' service or application name.Affected if UniFi Protect is not installed or not in use, the vulnerability does not apply.
-
Check UniFi Protect versionAccess the UniFi Protect controller UI, typically via the UniFi OS console. Navigate to Settings > System > About, or check the firmware/software version displayed. Compare your installed version against the affected version range provided by Ubiquiti security advisories.Affected if Your version falls within the known affected version range.
-
Verify Auto-Adopt Bridge Devices settingIn the UniFi Protect controller UI, go to Settings > General > Auto-Adopt Bridge Devices. Inspect whether this toggle is enabled. Alternatively, check via CLI if you have SSH access to the UniFi OS device using the 'ubnt-cli' or API calls to the Protect controller.Affected if Auto-Adopt Bridge Devices is currently enabled - this is the required condition for the bypass to work.
-
Assess network topologyReview your network segmentation to determine if cameras and untrusted devices share the same Layer 2 network segment or VLAN. Check switch configurations and camera port assignments.Affected if Cameras are reachable from the same network segment where untrusted or guest devices operate.
You are affected if UniFi Protect is running with Auto-Adopt Bridge Devices enabled, your version is within the affected range, and cameras are accessible from a network segment with adjacent untrusted devices.
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.
From vendor dataApply vendor patches from Ubiquiti when available; until then, disable Auto-Adopt Bridge Devices if possible and implement strict network segmentation to limit adjacent network access to camera infrastructure.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23116 — 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-2025-23116 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