Summary
- Ubiquiti’s latest security bulletin contains 22 vulnerability disclosures spanning several UniFi product areas.
- At least one UniFi Protect command-injection flaw carries a critical CVSS score of 9.9.
- The breadth of affected infrastructure increases the importance of knowing which UniFi applications and versions are deployed.
Ubiquiti has issued a large security bulletin covering 22 vulnerabilities across its UniFi ecosystem, including critical flaws that can lead to command execution or privilege escalation on network-connected infrastructure.
Security Advisory Bulletin 067 was published on 26 August and covers multiple UniFi application families. One of the disclosed issues affects UniFi Protect and can allow a low-privileged actor with network access to exploit improper input validation and execute command injection on the host device.
Ubiquiti assigned that Protect issue a CVSS base score of 9.9, placing it in the critical range. The vendor says UniFi Protect versions 7.1.87 and earlier are affected and directs customers to update to version 7.2.105 or later.
The bulletin extends beyond a single application or vulnerability class. Its 22 entries span different components of the UniFi environment, with affected products including network, access, communications, device-management, and security functions. That breadth turns the release into an estate-management issue as much as an individual patching event.
Ubiquiti’s bulletin does not report active exploitation. The presence of critical severity ratings therefore describes potential technical impact rather than a confirmed campaign against UniFi installations.
That distinction is important for infrastructure products. High or critical CVSS ratings establish the seriousness of a vulnerability under defined conditions, but an organisation’s actual exposure also depends on the affected application, software version, network reachability, privilege requirements, configuration, and whether the vulnerable component is deployed at all.
UniFi environments can combine routing, switching, wireless connectivity, cameras, physical access, communications, and centralised administration. Where those functions share management infrastructure, weaknesses in one application can create a different class of operational risk from a conventional endpoint defect. Control of the management plane may affect several underlying services even when the initial vulnerability sits in one component.
The size of the bulletin also presents a visibility problem. Organisations that treat UniFi as a single product may not have an immediately reliable view of the individual applications, controllers, gateways, or appliances running in each location. Managed-service arrangements and branch deployments can add another layer of ownership, particularly where local devices are maintained outside a central software inventory.
Ubiquiti has published fixed versions alongside the individual vulnerability entries, making version identification the practical boundary between an affected and remediated installation. The bulletin does not support treating every UniFi deployment as equally exposed.
The advisory follows a separate Ubiquiti security bulletin in July containing another large set of vulnerabilities. Repeated multi-product disclosures do not by themselves indicate that the platform is being compromised at scale, but they reinforce the need to treat network and physical-security appliances as maintained software systems rather than static infrastructure.
For organisations with UniFi in production, the immediate issue is therefore not the headline count of vulnerabilities alone. It is whether the affected applications are present, which versions are running, and whether central management systems create a larger operational dependency around those components.
