Ubiquiti patches three max‑severity UniFi vulnerabilities: CVE‑2026‑77537, CVE‑2026‑77550, CVE‑2026‑77554

Ubiquiti has released fixes for three maximum‑severity security issues affecting UniFi software, with impacts that include command injection and authentication bypass. According to the vendor’s advisory and independent reporting, the flaws can be triggered over the network without prior authentication, and do not require user interaction. Given UniFi’s wide deployment, administrators should review their environments and update quickly.

What’s confirmed

On August 26, 2026, Ubiquiti published Security Advisory Bulletin 067 detailing multiple vulnerabilities across the UniFi portfolio. Reporting from BleepingComputer highlights three “max‑severity” issues that received immediate patches:

• CVE‑2026‑77537 (UniFi Protect Application): Improper input validation leading to command injection on the host device. The advisory describes network‑based exploitation with no privileges required and lists a critical impact (the advisory snippet shows a CVSS base score of 10.0 for this item). Ubiquiti provides fixes in UniFi Protect Application 7.2.105 or later.
• CVE‑2026‑77550 (UniFi OS devices/instances): Improper neutralization of CRLF sequences (CRLF injection) enabling authentication bypass on certain devices running UniFi OS. BleepingComputer notes that this can be exploited remotely without privileges. The vendor states patches are available; exact affected versions for all devices are not fully enumerated in the snippet we reviewed.
• CVE‑2026‑77554 (UniFi Talk Application): Improper input validation leading to command injection in the UniFi Talk VoIP platform. BleepingComputer reports that fixes are provided in UniFi Talk Application 5.3.2 or later.

The advisory also lists many additional high‑ and critical‑severity issues across UniFi OS, Network Application, Protect, Connect, and other components. Those are outside the scope of this brief, but they reinforce the need to review the full bulletin for product‑specific guidance.

Why it matters: BleepingComputer reports that Ubiquiti has not disclosed evidence of in‑the‑wild exploitation for these three CVEs. However, the company characterizes the attacks as low complexity and not requiring user interaction. Separately, internet scan data cited in the same report suggests a large number of UniFi OS instances are (or have been) exposed online. Even though such counts may include historical results or honeypots, UniFi gear is an attractive target, and past botnet activity has abused unpatched network devices.

Practical next steps

Based on the vendor bulletin and the public reporting reviewed, a cautious, prioritized approach is reasonable:

• Update UniFi Protect Application to 7.2.105 or later (addresses CVE‑2026‑77537).
• Update UniFi Talk Application to 5.3.2 or later (addresses CVE‑2026‑77554).
• Review Security Advisory Bulletin 067 from Ubiquiti to identify the specific UniFi OS versions and device families impacted by CVE‑2026‑77550 and apply the vendor’s recommended updates for your models.
• Limit network exposure of UniFi management interfaces. Where possible, require VPN or management from trusted segments only.
• Monitor for unusual administrative activity and configuration changes on UniFi controllers and appliances after patching.

Important caveats

Some details remain incomplete in the material we reviewed:

• For CVE‑2026‑77550 (CRLF injection/authentication bypass), the exact list of affected UniFi OS versions and device models is not fully specified in the excerpted advisory text. The bulletin indicates patches exist, but administrators should consult the full advisory to match versions to their deployments.
• There is no confirmed information here about exploitation in the wild. Both sources emphasize risk (unauthenticated, low‑complexity network attacks) but do not assert active abuse at the time of publication.

The advisory language frequently refers to “access to the network,” while BleepingComputer describes exploitation “remotely without privileges.” In practice, treat any network‑reachable management surface as within scope—including internet‑exposed controllers and devices, jump hosts, or flat internal segments—until updates are applied.

Sources and further reading

• Ubiquiti Security Advisory Bulletin 067: https://community.ui.com/releases/Security-Advisory-Bulletin-067/fc4a3488-7c43-4628-8bab-f715e96dbfc9
• BleepingComputer coverage: https://www.bleepingcomputer.com/news/security/ubiquiti-patches-three-max-severity-security-vulnerabilities/

Bottom line

Three maximum‑severity UniFi vulnerabilities—CVE‑2026‑77537, CVE‑2026‑77550, and CVE‑2026‑77554—are patched and can be exploited over the network without prior authentication. Update UniFi Protect and Talk to the fixed releases, review the vendor bulletin for UniFi OS guidance, and reduce exposure of management services while you validate and roll out updates.

Alex Mira

Alex Mira is a fictitious AI-assisted author created for the Toolslib blog. Designed to support cybersecurity education, Alex writes about malware trends, software utilities, privacy practices, Windows internals, and practical defensive workflows. Articles published under Alex’s name are generated or assisted by AI and reviewed according to Toolslib’s editorial standards before publication.