Are your UniFi Access applications still on 4.3.22 or earlier?
Ubiquiti's Security Advisory Bulletin 073 covers seven vulnerabilities in UniFi Access Application. The bulletin lists 4.3.22 and earlier as affected. Official CVE records also treat every version before 4.3.24 as affected, so 4.3.23 is in scope. Four flaws are scored CVSS 3.1 9.9 Critical by Ubiquiti, including root code execution on the host device, privilege escalation within UniFi OS, and arbitrary commands on certain adopted Access devices. The fix is UniFi Access Application 4.3.24 or later. That release has been published since 27 October 2026, but check the running version. Do not assume an automatic update has landed or has stayed in place.
Critical (four CVEs at CVSS 3.1 9.9, Ubiquiti). Bulletin 073 became public on the Ubiquiti Community at 04:32 GMT on 19 November 2026. The advisory body is dated 18 November 2026, with no time or timezone. NVD published the seven CVE records at 05:18 GMT on 19 November 2026. No exploitation reported by Ubiquiti or CISA as of 19 Nov 2026. None of the seven were in CISA KEV when we checked at 05:40 GMT on 19 November 2026. Absence from that catalogue is not a finding that the flaws have not been exploited.
Update UniFi Access Application to 4.3.24 or later. The 4.3.24 release notes were published at 16:04 GMT on 27 October 2026 and list bugfixes, without mentioning these CVEs, which were reserved later. Confirm what is actually running on each console.
By Simon Phillips, CTO. Reviewed by Oliver Legg, Head of SOC and IR. Last updated 19 November 2026, 06:15 GMT.
At a Glance
Based on Ubiquiti Bulletin 073, the UniFi Access Application 4.3.24 release notes, the official CVE records, NVD and a CISA KEV check at 05:40 GMT on 19 November 2026. Last updated 19 November 2026, 06:15 GMT.
Critical (CVSS 3.1 9.9, Ubiquiti)
Four of seven CVEs carry that score. Ubiquiti also scores CVE-2026-132807 9.0 Critical, CVE-2026-132806 8.8 High and CVE-2026-132805 8.3 High. CVE-2026-132805 and CVE-2026-132807 need no login. CVE-2026-132806 is the only one with unchanged scope (S:U). NVD status is Received and has not published its own scores.
Fix available, check versions
Update to 4.3.24 or later. The 4.3.24 release notes were published on 27 October 2026. Check the running version. Do not assume an automatic update has been applied or has stayed in place.
4.3.22 and earlier, plus 4.3.23
Bulletin 073 lists 4.3.22 and earlier. Official CVE records and NVD list every version before 4.3.24, so 4.3.23 is in scope even though the bulletin does not name it. The Access application runs on UniFi OS and can affect the host, UniFi OS and certain adopted Access devices.
4.3.24 or later
That is the only mitigation Ubiquiti lists for all seven CVEs. Confirm the running UniFi Access Application version on every console.
UniFi Access Application 4.3.24 release notes are published on the Ubiquiti Community. The notes list bugfixes and do not mention these CVEs, which were reserved later.
Bulletin 073 is dated Version 1.0, Revision 1.0. The document date has no time or timezone.
The Bulletin 073 page is first published on the Ubiquiti Community (article:published_time 2026-11-19T04:32:04Z). Official CVE records for CVE-2026-132802 to CVE-2026-132808 are published at 04:32 GMT.
NVD publishes the seven records, status Received. At 05:40 GMT on 19 November 2026, none of the seven CVEs are in CISA KEV (catalogue 2026.11.18). No exploitation reported by Ubiquiti or CISA as of 19 Nov 2026.
What the flaws do
Wording below is from Bulletin 073 and the matching NVD records. Scores and vectors are Ubiquiti's CVSS 3.1 values. All seven share the same vendor mitigation: update UniFi Access Application to 4.3.24 or later.
- CVE-2026-132802, CVSS 3.1 9.9 Critical (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. A malicious actor with access to the network and low privileges could exploit an Improper Link Resolution Before File Access vulnerability found in UniFi Access Application to execute arbitrary code with root privileges on the host device. Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132803, CVSS 3.1 9.9 Critical (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. A malicious actor with access to the network and low privileges could exploit a series of authenticated SQL Injection vulnerabilities found in UniFi Access Application to escalate privileges on the host device. Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132804, CVSS 3.1 9.9 Critical (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to escalate privileges within UniFi OS. Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132805, CVSS 3.1 8.3 High (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L. A malicious actor with access to the network could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to obtain information and make unauthorized changes on the host device. This CVE needs no login (PR:N). It is not a low-privilege-account flaw. Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132806, CVSS 3.1 8.8 High (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. A malicious actor with access to the network and low privileges could exploit an authenticated SQL Injection vulnerability found in UniFi Access Application to obtain sensitive information and make unauthorized changes within the UniFi Access Application. This is the only CVE of the seven with unchanged scope (S:U). Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132807, CVSS 3.1 9.0 Critical (Ubiquiti), CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. A malicious actor with access to the network and under certain conditions could exploit an Improper Certificate Validation vulnerability found in UniFi Access Application to obtain sensitive information from and make unauthorized changes to an adopted UniFi Access device. This CVE needs no login, but is harder to pull off (PR:N, AC:H). Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
- CVE-2026-132808, CVSS 3.1 9.9 Critical (Ubiquiti), CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. A malicious actor with access to the network and low privileges could exploit an Incorrect Authorization vulnerability found in UniFi Access Application to execute arbitrary commands on certain adopted UniFi Access devices. Affected product in the bulletin: UniFi Access Application 4.3.22 and earlier. Official CVE records also treat every version before 4.3.24 as affected, including 4.3.23. Mitigation: 4.3.24 or later.
What to Do in the Next 24 Hours
Vendor advice and our advice are labelled separately. Tick both tracks.
Update to 4.3.24 or later
- Ubiquiti's mitigation for every CVE in Bulletin 073 is to update UniFi Access Application to Version 4.3.24 or later.
- The bulletin lists the affected product as UniFi Access Application, Version 4.3.22 and earlier.
- The official CVE records and NVD entries list every version before 4.3.24 as affected, so 4.3.23 is in scope even though the bulletin does not name it.
- Ubiquiti does not list any other mitigation in Bulletin 073.
Inventory, confirm the version, then reduce exposure
- Inventory every UniFi OS console that runs UniFi Access Application and record the Access application version.
- Treat anything below 4.3.24 as in scope, including 4.3.23. 4.3.24 has been published since 27 October 2026, but check the running version. Automatic updates can be off, and a user comment on the 4.3.24 release notes describes turning them off and going back to 4.3.22.
- Keep UniFi OS and Access management off the public internet, for example on a management VLAN or VPN.
- Review local and cloud accounts, especially low-privilege or shared ones, and enforce MFA. Five of the seven CVEs need low privileges. CVE-2026-132805 and CVE-2026-132807 need no login.
- Segment Access hubs, readers and controllers from general user networks.
Proactive: Find Exposure and Patch
Find every Access application, confirm the version, apply Ubiquiti's 4.3.24 or later fix, and reduce how far a low-privilege or unauthenticated request can reach.
Inventory every UniFi Access application
Our advice is to search configuration management, RMM and site inventories for UniFi OS consoles that run UniFi Access Application. Record the Access application version, not only that the application is installed. Include sites you manage for customers as well as your own.
Confirm the running version
Bulletin 073 lists 4.3.22 and earlier as affected. The official CVE records and NVD list every version before 4.3.24, so 4.3.23 is in scope even though the bulletin does not name it. Treat anything below 4.3.24 as in scope. If a console already shows 4.3.24 or later, confirm that yourself. Do not assume an automatic update has been applied or has stayed in place.
Update to 4.3.24 or later
This is the vendor fix. Ubiquiti lists no other mitigation. The 4.3.24 release notes were published at 16:04 GMT on 27 October 2026. After the update, confirm the running version again.
Take management off the public internet
Our advice, because all seven issues are network-reachable and two of them need no login. Keep UniFi OS and Access management interfaces off the public internet, and restrict them to a management VLAN or VPN. Do not treat a public management port as acceptable even after you have updated.
Tighten accounts and MFA
Our advice, because five of the seven CVEs require low privileges. Review local and cloud UniFi accounts, remove or replace shared and unused logins, and enforce MFA. Pay attention to low-privilege accounts, not only administrators. This does not reduce the risk from CVE-2026-132805 or CVE-2026-132807, which need no login.
Segment Access devices
Our advice. Two of the Critical CVEs can affect adopted UniFi Access devices, including information disclosure, unauthorised changes, and arbitrary commands on certain adopted devices. Keep hubs, readers and controllers segmented from general user networks, and review the adoption list for devices you do not recognise.
Free Detection Pack
Built by the CybaVerse threat hunt team for businesses, internal IT teams and MSPs. Pack version 1.0.0 is the download on this page. Check the Access application version offline, and hunt for account, policy, unlock and console traffic leads. Everything is read-only.
check-unifi-access.sh
A read-only, offline bash checker. It reads a version string, a saved application list or log, a JSON export, or an extracted support file, and judges the UniFi Access Application version against 4.3.24. It never touches the network, never runs UniFi tools, never writes a file and never prints secrets. It treats every version below 4.3.24 as affected, including 4.3.23.
bash check-unifi-access.sh --version 4.3.22
bash check-unifi-access.sh --file dpkg-l.txt --json apps.json --dir ./support-extractedCheck-UnifiAccess.ps1
The same checks in PowerShell, with the same options, output and exit codes.
pwsh -File .\Check-UnifiAccess.ps1 -Version 4.3.9+12130 -Dir ./support-extractedKQL hunts and Sigma rules
8 KQL hunts for Microsoft Sentinel, and 9 Sigma rules, covering admin and account changes, door policy, lockdown and unlock activity, internet exposure of management ports, unusual console outbound traffic, and scripted connections to Access. All of these hunts are our patterns. Access log field names are unverified, so several hunts match on keywords. Tune them on your own data.
Exit codes
| Code | Meaning |
|---|---|
| 0 | FIXED: every source shows Access Application 4.3.24 or later |
| 2 | AFFECTED: a source shows a version below 4.3.24, including 4.3.23 |
| 3 | UNKNOWN or REVIEW: no version found, mixed versions in one source, or an incomplete scan |
| 5 | USAGE OR READ ERROR |
Exit code 1 is reserved and is not used.
Know the limits
- Both checkers are read-only and offline. They never run UniFi tools, never use the network, never write files and never print secrets.
- The KQL has not been run against a live tenant. The Sigma rules were checked and converted, not run against live data.
- Ubiquiti does not document Access log fields, so the Access-related hunts are marked unverified and match on keywords. Check them against a few real events before you rely on them.
Reactive: How to Hunt (Our Advice)
This is our advice, not vendor hunting guidance. Bulletin 073 does not include detection steps. The free pack on this page has hunts you can run. Look for misuse of Access, the host and UniFi OS after you have confirmed the version.
Unexpected accounts and role changes
Look for new local or cloud UniFi administrator accounts, unexpected role or permission changes, and shared or low-privilege accounts that have been used in unusual ways. Five of these flaws need only low privileges to start. CVE-2026-132805 and CVE-2026-132807 need no login, so also look for unauthenticated reachability of management interfaces.
Door policy, schedule and lockdown changes
Review Access policies, schedules and emergency lockdown settings for changes nobody authorised. Unexpected changes can be a sign that the Access application or an adopted device has been misused.
Unexplained unlock events
Review unlock activity and door events that do not match known users, known hours or a known incident. Compare them with the people and credentials you expect to have access.
Odd outbound requests from the console
Two of the CVEs are SSRF issues, and CVE-2026-132805 needs no login. Look for unusual outbound requests or connections from the UniFi OS console or the Access application host that you cannot explain.
Unexpected processes or files on the host
CVE-2026-132802 can lead to root code execution on the host device, and CVE-2026-132803 can escalate privileges on the host. Look for unfamiliar processes, scheduled tasks or files on the console.
If you suspect compromise (our advice)
- Update UniFi Access Application to 4.3.24 or later if it is not already on a fixed release, then confirm the running version.
- Rotate UniFi administrator and SSO credentials, and review local and cloud accounts for unexpected additions or role changes.
- Review the Access device adoption list and re-adopt anything you do not recognise.
- Export logs before you make further changes.
- If you believe the console is compromised, consider a factory reset and a restore from a known-good backup.
UniFi Access Bulletin 073 FAQ
Short answers based on Ubiquiti Bulletin 073, the 4.3.24 release notes, the official CVE records, NVD and a CISA KEV check at 05:40 GMT on 19 November 2026. Last updated 19 November 2026, 06:15 GMT.
Am I affected?
You are in scope if you run UniFi Access Application 4.3.22 or earlier, which is the affected range Ubiquiti gives in Bulletin 073. The official CVE records and NVD entries list every version before 4.3.24 as affected, so 4.3.23 is in scope even though the bulletin does not name it. The mitigation for all seven CVEs is to update to version 4.3.24 or later. If a console already shows 4.3.24 or later, confirm the running version. Automatic updates can be off, and a user comment on the 4.3.24 release notes describes turning them off and going back to 4.3.22.
What is the severity?
Ubiquiti, as the CVE assigner, scores four of the seven flaws CVSS 3.1 9.9 Critical: CVE-2026-132802, CVE-2026-132803, CVE-2026-132804 and CVE-2026-132808. It scores CVE-2026-132807 9.0 Critical, CVE-2026-132806 8.8 High and CVE-2026-132805 8.3 High. All seven are network-reachable. Five require low privileges: CVE-2026-132802, CVE-2026-132803, CVE-2026-132804, CVE-2026-132806 and CVE-2026-132808. CVE-2026-132805 needs no login (PR:N); it is not a low-privilege-account flaw. CVE-2026-132807 also needs no login, but is harder to pull off (PR:N and AC:H), and in Ubiquiti's wording applies under certain conditions. CVE-2026-132806 is the only one with unchanged scope (S:U). The other six have changed scope (S:C). NVD has received the records and has not published its own scores. We show Ubiquiti's scores.
Is there a patch?
Yes. Ubiquiti's mitigation for every CVE in Bulletin 073 is to update UniFi Access Application to version 4.3.24 or later. The 4.3.24 release notes were published on the Ubiquiti Community at 16:04 GMT on 27 October 2026. Those notes list bugfixes and do not mention these CVEs, which were reserved on 19 November 2026. Treat 4.3.24 or later as the fixed range, and confirm what is actually running. The official CVE records treat every version below 4.3.24 as affected, including 4.3.23.
I turn on automatic updates. Do I still need to check?
Yes. Our advice is to record the UniFi Access Application version on every UniFi OS console you manage. 4.3.24 has been published since 27 October 2026, so some consoles may already be on a fixed release, but do not assume an automatic update has been applied or has stayed in place. A user comment on the 4.3.24 release notes describes turning automatic updates off and going back to 4.3.22. Check the running version.
What access does an attacker need?
Take the wording from the bulletin and the NVD records, which match. For CVE-2026-132802, CVE-2026-132803, CVE-2026-132804, CVE-2026-132806 and CVE-2026-132808, Ubiquiti says a malicious actor with access to the network and low privileges could exploit the issue. CVE-2026-132805 needs no login (PR:N): Ubiquiti says a malicious actor with access to the network, with no privilege requirement in the text. CVE-2026-132807 also needs no login, but is harder to pull off (PR:N, AC:H), and Ubiquiti says it applies under certain conditions. CVE-2026-132806 is the only one with unchanged scope (S:U). Several of the 9.9-rated issues can lead to root code execution on the host, privilege escalation within UniFi OS, or arbitrary commands on certain adopted Access devices.
Has this been exploited?
No exploitation reported by Ubiquiti or CISA as of 19 Nov 2026. None of the seven CVEs were in CISA's Known Exploited Vulnerabilities catalogue when we checked at 05:40 GMT on 19 November 2026 (catalogue version 2026.11.18, released 19:17 GMT on 18 November 2026). Absence from that catalogue is not a finding that the flaws have not been exploited.
What should I do if I suspect compromise?
This is our advice, not vendor advice. Update UniFi Access Application to 4.3.24 or later. Rotate UniFi administrator and SSO credentials, and review local and cloud accounts for unexpected additions or role changes. Review the Access device adoption list and re-adopt anything you do not recognise. Look for door policy, schedule, lockdown or unlock events that nobody authorised. Export logs before you make further changes. If you believe the console is compromised, consider a factory reset and a restore from a known-good backup.
We are an MSP or manage many UniFi sites. Where do we start?
Inventory every UniFi OS console that runs UniFi Access Application and record the Access application version. Update anything below 4.3.24, including 4.3.23, which the official CVE records treat as affected even though Bulletin 073 only names 4.3.22 and earlier. Check the running version. Do not assume automatic updates have already landed or have stayed in place. Keep UniFi OS and Access management off the public internet, tighten low-privilege and shared accounts, and enforce MFA. Then review account, role, policy and unlock changes, and odd outbound activity from each console. The free detection pack on this page can check versions offline and includes hunts. If you need help doing that across the estates you manage, contact CybaVerse.
Need help finding UniFi Access across the estates you manage?
CybaOps monitors your servers, endpoints and cloud workloads, whether that's your own business or your clients'. UK-based analysts monitor alerts 24/7, run these threat hunts and act on pre-approved response actions, and CybaOps drives remediation through to a verified fix, so proactive checks and reactive response happen in one place.
Sources
- Ubiquiti: Security Advisory Bulletin 073 (community page first published 04:32 GMT, 19 November 2026; advisory body dated 18 November 2026)
- Ubiquiti: UniFi Access Application 4.3.24 release notes (published 16:04 GMT, 27 October 2026)
- NVD: CVE-2026-132802 (published 05:18 GMT, 19 November 2026)
- NVD: CVE-2026-132803
- NVD: CVE-2026-132804
- NVD: CVE-2026-132805
- NVD: CVE-2026-132806
- NVD: CVE-2026-132807
- NVD: CVE-2026-132808
- CISA Known Exploited Vulnerabilities catalogue (checked 05:40 GMT on 19 November 2026; catalogue version 2026.11.18)
Related threat guides: HPE Aruba AOS critical flaws. Check Point Gaia CVE-2026-123039. Zyxel CPE/ONT extender CVE-2026-79614. All threat guides.