What happened
Ubiquiti has published Security Advisory Bulletin 073 covering the UniFi Access application. UniFi Access is building access control software: it manages card readers, electronic locks and intercoms and runs on UniFi OS consoles. On November 19, 2026, four related entries appeared in the US vulnerability database NVD: CVE-2026-132802, CVE-2026-132803, CVE-2026-132804 and CVE-2026-132808.
All four are rated CVSS 9.9 out of 10, which is critical. They are four different bugs: improper handling of file links, a series of SQL injection flaws, a server-side request forgery (SSRF) flaw and an authorization flaw. What they share is that the attacker needs network access and an account, even one with low privileges.
No exploitation of these flaws is known so far. As of November 19, 2026, they are not in the CISA KEV catalog, and ENISA’s European vulnerability database EUVD does not list them as exploited either. That can change quickly, so do not put off the update.
Why it is dangerous
According to the NVD descriptions, an attacker with network access and low privileges could achieve the following:
- CVE-2026-132802 (CWE-59, improper link resolution): run arbitrary code with root privileges on the device hosting the application. Think of a shortcut someone quietly redirects: the program believes it is working with a harmless file, but it is actually changing a system file.
- CVE-2026-132803 (CWE-89, SQL injection): escalate privileges on the host device. The application puts user input into a database command, and the attacker smuggles in instructions of their own.
- CVE-2026-132804 (CWE-918, SSRF): escalate privileges within UniFi OS. The server can be tricked into sending requests on the attacker’s behalf to places the attacker cannot reach, much like a receptionist helpfully transferring a call to an internal line.
- CVE-2026-132808 (CWE-863, incorrect authorization): run arbitrary commands on certain adopted UniFi Access devices. The system checks that you are logged in, but not whether you are allowed to do that specific thing.
The attack works over the network and needs no action from a victim, but it does require a login with at least low privileges. Such an account may belong to an employee or an outside technician, or be obtained through a stolen password. Whoever controls the console as root could read and change data about people and access rights and use the device as a stepping stone into other parts of the network.
CVSS is a severity scale from 0 to 10. The 9.9 score (CVSS 3.1) shown in NVD was not assigned by NVD itself, but by another organization that the record identifies only by an ID. EPSS estimates the chance of exploitation in the next 30 days, and as of November 19, 2026 it ranges from 0.26% to 0.58%, which is low for now. The CISA KEV catalog lists flaws with confirmed exploitation, and these four are not on it.
Who is affected
The flaws affect Ubiquiti’s UniFi Access application. The NVD records do not list specific affected or fixed versions. You will find them in the vendor’s Security Advisory Bulletin 073 on community.ui.com.
UniFi Access is typically used in offices, schools, coworking spaces, apartment buildings and smaller campuses to open doors with a card, a phone or an intercom. The application runs on a UniFi OS console. CVE-2026-132808 also affects certain adopted UniFi Access devices, and the vendor specifies which ones.
The highest risk is in networks where many people can reach the console, or where its management interface is exposed to the internet. If you do not use UniFi Access and run, for example, only UniFi Network, these four flaws do not affect you based on the NVD descriptions.
How to check if you are affected
The easiest way is the UniFi OS console’s web interface. In the console settings, in the section for applications and updates (called Control Plane in newer versions), you will see the installed version of the Access application. If you manage the console remotely, the same overview is available at unifi.ui.com.
Compare the version with the information in Bulletin 073. The firmware of individual Access devices, such as readers, hubs and intercoms, is shown in the device list inside the Access application.
If SSH is enabled on the console, this read-only command lists the installed UniFi packages without changing anything:
dpkg -l | grep -i unifi
How to fix it
Ubiquiti lists the fixed versions in Security Advisory Bulletin 073. It is the only authoritative source, as the NVD records contain no version numbers. Work through it in this order:
- Open Bulletin 073 on community.ui.com and find out which UniFi Access version fixes the flaws.
- Back up the console and schedule a short maintenance window. Door readers may not work during the update, so have a key or another way in ready.
- Update the UniFi Access application in UniFi OS to the version named in the bulletin. If the vendor requires it, update UniFi OS itself as well.
- If the bulletin also lists firmware updates for the adopted Access devices affected by CVE-2026-132808, install them.
- After updating, confirm the version and test that doors open correctly.
The NVD records do not mention a workaround, so check with the vendor whether the bulletin includes one. Until you have patched, apply general measures: keep the console’s management interface off the internet, allow only what is strictly necessary into the network with your Access devices, and remove unneeded accounts in both UniFi OS and the Access application. Change passwords on shared accounts and turn on two-factor authentication.
The flaws are not in the CISA KEV catalog, so CISA has not set a mandatory remediation deadline. With a 9.9 score, it is still sensible to update within a few days.
What if you may already be compromised
The NVD records do not list specific indicators of compromise. Look for the usual signs:
- User and admin lists in UniFi OS and the Access application: unknown accounts or accounts with unexpectedly higher privileges.
- The console’s system and audit logs: logins from unfamiliar addresses and configuration changes nobody on your team made.
- Door unlock records and changes to access rules, cards and groups outside your normal processes.
- Unusual behavior of the console or Access devices: unexpected reboots, high load, or connections to unknown addresses in your firewall logs.
If you find anything suspicious, disconnect the console from the internet, preserve the logs without deleting them, and bring in an incident response specialist. If root-level access is suspected, updating alone is not enough, and the device may need a factory reset and a fresh setup. Change all passwords and consider whether you need to report the incident, for example if personal data may have leaked.