CVE-2026-50746
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 network could exploit an Improper Access Control vulnerability found in UniFi Connect Application to execute a Command Injection on the host device.
In the news
Third-party coverage- Ubiquiti warns of new max severity UniFi OS vulnerability
- Ubiquiti Patches Critical UniFi Flaws Across Connect, Talk, Access ...
- Ubiquiti Patches Critical UniFi OS Flaws Allowing Command Injection ...
- Weekly Recap: ShareFile Threat, Citrix Bleed 2 Ransomware, AI ...
- CVE-2026-50746 Archives - Security Affairs
Surfaced from public web coverage — external links open in a new tab.
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 vulnerability in UniFi Connect Application involves improper access control that allows a malicious actor with network access to inject and execute arbitrary commands on the host device. The combination of access control failure and command injection results in complete system compromise with CVSS 10 severity.
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< 3.24.20CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify UniFi Connect Application installationLocate the UniFi Connect Application installation and determine its version number. This may be found in the application itself, a package manager, or system inventory tools.Affected if Version is present and less than 3.4.20
-
Compare installed version to affected rangeCompare the identified version number against the affected range: versions earlier than 3.4.20 are vulnerable.Affected if Installed version is lower than 3.4.20
-
Verify network exposure of UniFi Connect interfaceDetermine if the UniFi Connect Application management interface is accessible over the network. Check firewall rules, network segmentation, and interface bindings.Affected if The interface is reachable from network segments that contain untrusted users or systems
You are affected if the UniFi Connect Application version is below 3.4.20 and the interface is accessible over the network.
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 · scoped3.24.20
Apply vendor patches immediately when available and implement network segmentation to restrict access to UniFi Connect systems to only authorized personnel and trusted network segments.
3.4.20
- Log in to the UniFi Connect Application admin interface
- Navigate to the Settings or System section
- Check the current installed version to confirm it is below 3.4.20
- Locate the firmware/software update option within the application settings
- Initiate the update to version 3.4.20 or later
- Verify the upgrade completed successfully by checking the version number post-update
- Confirm the application is functioning normally after the upgrade
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-50746 — 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-50746 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