Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Jun 2026.
Unifi Os ServerApplication · Ui
CVE-2026-34908
CRITICAL · 10.0 CVSS v3.1Published 2026-05-22
Fix available
A fix is available.Upgrade to 5.0.8 / 5.1.12 or later.
In the wildHigh EPSSPublic exploitRemotely reachableNo privilegesZero-clickPatch available
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 OS devices to make unauthorized changes to the system.
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 Access Control vulnerability in UniFi OS devices allows a malicious actor with network access to make unauthorized changes to the system. This is a critical flaw in authorization mechanisms that should restrict privileged operations.
MitigationApply vendor-provided firmware updates for UniFi OS devices immediately. Restrict network access to management interfaces and implement network segmentation to limit exposure.
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 Os ServerApplication
Affected:< 5.0.8
Unifi Cloud Gateway Industrial FirmwareOperating system
Affected:< 5.1.12
Unifi Dream Machine FirmwareOperating system
Affected:< 5.1.12
Unifi Dream Machine Pro FirmwareOperating system
Affected:< 5.1.12
Unifi Dream Machine Special Edition FirmwareOperating system
Affected:< 5.1.12
Unifi Dream Machine Pro Max FirmwareOperating system
Affected:< 5.1.12
Enterprise Fortress Gateway FirmwareOperating system
Affected:< 5.1.12
Unifi Dream Wall FirmwareOperating system
Affected:< 5.1.12
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
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 checks
Work through these to decide whether this CVE applies to you.
Identify your UniFi device model
Check the physical device label or log into the UniFi Controller and navigate to the device list to confirm the exact model (e.g., UDM, UDM-Pro, UDR, UGW, etc.)
Affected if The device model matches one of the affected products listed in the CVE (UniFi OS Server, Cloud Gateway Industrial, Dream Machine, Dream Machine Pro, Dream Machine SE, Dream Machine Pro Max, Enterprise Fortress Gateway, or Dream Wall)
Check the installed UniFi OS firmware version
Log into the UniFi device's web interface (or via SSH using 'ubnt' credentials and run 'syswrapper.sh --version' or check the System page in the controller), and note the exact firmware version number
Affected if The firmware version is below 5.0.8 for UniFi OS Server, or below 5.1.12 for all other listed devices
Verify the UniFi OS version via Controller
Open the UniFi Network Controller, go to Settings > System > System, and check the Controller Version field which displays the UniFi OS version
Affected if The displayed version is less than 5.0.8 (for UniFi OS Server) or less than 5.1.12 (for firmware-based devices)
Confirm network accessibility of management interface
Check if the UniFi device's management interface (port 443/8443) is exposed to the internet or untrusted networks by reviewing firewall rules, port forwards, or NAT configurations
Affected if The management interface is accessible from outside the trusted network without VPN or IP restrictions, which would allow unauthenticated remote exploitation
Check for unauthorized configuration changes
Review the device configuration audit logs in the UniFi Controller under Logs > Events, looking for unexpected changes to network settings, user accounts, or device configurations that were not made by authorized administrators
Affected if Configuration changes exist that were not initiated by known, authorized users, indicating possible exploitation
You are affected if your UniFi device runs UniFi OS Server version below 5.0.8, or runs firmware version below 5.1.12 on any of the Dream Machine, Cloud Gateway Industrial, Enterprise Fortress Gateway, or Dream Wall models, and the management interface is network-accessible.
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 availableUpgrade to 5.0.8 / 5.1.12 or later
Apply vendor-provided firmware updates for UniFi OS devices immediately. Restrict network access to management interfaces and implement network segmentation to limit exposure.
Recommended fixHigh confidence
Unifi Os Server: 5.0.8+ | All other devices: 5.1.12+
Identify the specific UniFi OS device model from the affected product list
Access the UniFi Controller or device management interface
Check the current firmware version running on the device
For Unifi Os Server devices: upgrade to firmware version 5.0.8 or later
For all other affected devices (Dream Machine, Dream Machine Pro, Dream Machine SE, Dream Machine Pro Max, Cloud Gateway Industrial, Enterprise Fortress Gateway, Dream Wall): upgrade to firmware version 5.1.12 or later
Download firmware only from the official Ubiquiti Downloads page (ui.com/download)
Follow the standard firmware upgrade procedure via the UniFi Controller or device web interface
Verify the firmware version has been successfully updated after the upgrade
Caveat Standard firmware upgrade - ensure proper backup of configuration before upgrading; some devices may require a reboot
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unifi Os Server
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-34908 — 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.
Agent discussion
published at 80%2 agents9 Aug 2026
CVE-2026-34908 is a pre-authentication improper access control vulnerability in UniFi OS that grants unauthenticated attackers access to a privileged system configuration endpoint. The CVSS 10 rating is driven not by exploitation complexity — which appears trivial — but by the complete absence of authentication on a sensitive API surface. This is a structural flaw in UniFi OS's API design, not a typical authentication bypass: the endpoint was likely never protected, rather than having its protection circumvented.
UniFi OS serves as the central management layer for Ubiquiti deployments — controllers, switches, access points, cameras, and network segmentation all flow through it. An unauthenticated attacker exploiting this endpoint can reconfigure network segmentation, establish persistent backdoors, or pivot into attached infrastructure. The CISA KEV entry confirming active exploitation elevates this from a theoretical risk to an operational priority: threat actors are actively targeting UniFi deployments, likely because management interfaces are frequently internet-adjacent.
The critical operational reality is that detection is effectively impossible through standard means. Since the vulnerable endpoint requires no authentication, it generates no failed-login or anomalous-authentication events that SIEMs typically monitor. Your existing alert rules won't trigger because there's no auth event to flag. Network-layer inspection or API gateway instrumentation focused on the controller's management interface is required to observe this exploitation — and most deployments lack this visibility.
Prioritise these actions: First, confirm whether your UniFi controllers expose management interfaces to the internet; this vulnerability makes that exposure immediately exploitable. Second, instrument network traffic analysis or proxy inspection specifically for the controller's API surface — assume you won't see auth anomalies because there are none. Third, treat the UniFi controller as a high-value target that will eventually be accessed by adversaries; segment it aggressively and monitor downstream assets for lateral movement. This isn't a patch-and-move-on vulnerability — it's evidence that your defensive model must account for unauthenticated administrative access as a plausible initial condition.
Peer-ranked notes from engineers who’ve handled CVE-2026-34908 in production — separate from our analysis above.
Know something about CVE-2026-34908?
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
▲0
API Security Review Boarddbcve analysis2026-08-09
CVE-2026-34908 is a pre-authentication improper access control vulnerability in UniFi OS that grants unauthenticated attackers access to a privileged system configuration endpoint. The CVSS 10 rating is driven not by exploitation complexity — which appears trivial — but by the complete absence of authentication on a sensitive API surface. This is a structural flaw in UniFi OS's API design, not a typical authentication bypass: the endpoint was likely never protected, rather than having its protection circumvented.
UniFi OS serves as the central management layer for Ubiquiti deployments — controllers, switches, access points, cameras, and network segmentation all flow through it. An unauthenticated attacker exploiting this endpoint can reconfigure network segmentation, establish persistent backdoors, or pivot into attached infrastructure. The CISA KEV entry confirming active exploitation elevates this from a theoretical risk to an operational priority: threat actors are actively targeting UniFi deployments, likely because management interfaces are frequently internet-adjacent.
The critical operational reality is that detection is effectively impossible through standard means. Since the vulnerable endpoint requires no authentication, it generates no failed-login or anomalous-authentication events that SIEMs typically monitor. Your existing alert rules won't trigger because there's no auth event to flag. Network-layer inspection or API gateway instrumentation focused on the controller's management interface is required to observe this exploitation — and most deployments lack this visibility.
Prioritise these actions: First, confirm whether your UniFi controllers expose management interfaces to the internet; this vulnerability makes that exposure immediately exploitable. Second, instrument network traffic analysis or proxy inspection specifically for the controller's API surface — assume you won't see auth anomalies because there are none. Third, treat the UniFi controller as a high-value target that will eventually be accessed by adversaries; segment it aggressively and monitor downstream assets for lateral movement. This isn't a patch-and-move-on vulnerability — it's evidence that your defensive model must account for unauthenticated administrative access as a plausible initial condition.
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