# UniFi Access Application, Ubiquiti Security Advisory Bulletin 073 (CVE-2026-132802 to CVE-2026-132808): detection pack

Pack 1.0.0, CybaVerse threat hunt, 19 Nov 2026. hubfs `unifi-access-bulletin-073-pack-v1`. Our page:
https://www.cybaverse.co.uk/threats/unifi-access-bulletin-073

**Patch now regardless of KEV status:** update UniFi Access Application to **4.3.24 or later** on every UniFi OS console
that runs it. This is the only mitigation Ubiquiti lists for all seven CVEs.

- Not in CISA KEV (catalogue 2026.11.18, released 19:17 GMT on 18 Nov 2026; checked 05:40 GMT on 19 Nov 2026).
  KEV due dates under BOD 26-04 apply to US federal agencies only. Absence from KEV says nothing about whether these
  flaws are being used.
- No exploitation reported by Ubiquiti or CISA as of 19 Nov 2026. The bulletin does not mention exploitation.
- The KQL in this pack has NOT been run against a live tenant. It is parsed with Kusto.Language against the published
  Microsoft Learn table schemas only. The Sigma rules are not run against live data either. Tune both on your own data.
- There are no published IOCs for these CVEs, and this pack invents none. Every hunt is OUR PATTERN: a lead to review,
  not proof of compromise.
- Research is credited to security researchers only.

## The seven CVEs

Scores are Ubiquiti's (the CNA), CVSS 3.1. NVD shows the records as Received and has not published its own scores.
Access wording is from the bulletin and the CVE records.

| CVE | CWE | CVSS 3.1 (Ubiquiti) | Vector | Needs | Impact (bulletin) |
|---|---|---|---|---|---|
| CVE-2026-132802 | CWE-59 | 9.9 Critical | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H | network access and low privileges | code execution as root on the host device (improper link resolution) |
| CVE-2026-132803 | CWE-89 | 9.9 Critical | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H | network access and low privileges | privilege escalation on the host device (a series of authenticated SQL injections) |
| CVE-2026-132804 | CWE-918 | 9.9 Critical | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H | network access and low privileges | privilege escalation within UniFi OS (SSRF) |
| CVE-2026-132805 | CWE-918 | 8.3 High | AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L | network access, no privileges stated | information disclosure and unauthorised changes on the host device (SSRF) |
| CVE-2026-132806 | CWE-89 | 8.8 High | AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | network access and low privileges | information disclosure and unauthorised changes within the Access Application (authenticated SQL injection) |
| CVE-2026-132807 | CWE-295 | 9.0 Critical | AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H | network access, under certain conditions | information disclosure and changes on an adopted Access device (improper certificate validation) |
| CVE-2026-132808 | CWE-863 | 9.9 Critical | AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H | network access and low privileges | arbitrary commands on certain adopted Access devices (incorrect authorisation) |

## Affected and fixed versions

| Source | Affected | Fixed |
|---|---|---|
| Ubiquiti Bulletin 073 | UniFi Access Application 4.3.22 and earlier | 4.3.24 or later |
| CVE records (cve.org) and NVD | every version below 4.3.24 | 4.3.24 |

- **4.3.23:** the bulletin does not name it and we found no public 4.3.23 release, but the CVE records cover every version
  below 4.3.24. The checker treats 4.3.23 as AFFECTED and prints a note about the gap.
- **The 4.3.24 release notes were published at 16:04 GMT on 27 Oct 2026** (edited 30 Oct) and list bugfixes only. They do not
  mention these CVEs. A console set to update automatically may already be fixed, but check the running version: one
  user comment on the 4.3.24 release page describes turning automatic updates off and going back to 4.3.22.
- The bulletin covers the Access Application. It does not name console models or Access device firmware. Four-part
  device firmware versions (for example hub or reader firmware) are not Access Application versions, and the checker
  ignores them.

## Timeline (GMT)

- 27 Oct 2026, 16:04: UniFi Access Application 4.3.24 release notes published on the Ubiquiti Community.
- 18 Nov 2026: date in the Bulletin 073 body (Version 1.0, Revision 1.0; no time or timezone given).
- 19 Nov 2026, 04:32: Bulletin 073 community page first published; CVE records published by Ubiquiti.
- 19 Nov 2026, 05:18: NVD receives the seven records (status Received, no NVD scores).
- 19 Nov 2026, 05:40: KEV check, catalogue 2026.11.18; none of the seven listed.

## Corrections to the original flag

1. **4.3.23 is AFFECTED** according to the CVE records and NVD (versions below 4.3.24). The bulletin only says 4.3.22 and
   earlier. We show both and treat 4.3.23 as AFFECTED.
2. **4.3.24 release date:** published 16:04 GMT on 27 Oct 2026 and edited 30 Oct, so "late October" holds. The claim that it
   is on Ubiquiti's Official release channel is UNVERIFIED: the channel was not visible on the release page we loaded.
3. **The 4.3.24 release notes do not mention these CVEs**, so a console's update history is not proof of the fix. Check the
   running version.
4. **CVE-2026-132805 needs no privileges** (PR:N; the bulletin says only "access to the network"). It is not one of the
   low-privilege flaws.
5. **CVE-2026-132807 is PR:N with AC:H**, "under certain conditions"; **CVE-2026-132806 is scope unchanged (S:U)**, unlike
   the other six.
6. **The scores are Ubiquiti's (CNA), not NVD's.** NVD lists them as secondary CNA scores and has not assessed the records.
7. **Publication timing:** the bulletin body is dated 18 Nov 2026, but the community page and the CVE records went public
   at 04:32 GMT on 19 Nov 2026, and NVD received them at 05:18 GMT.
8. **Exploitation wording:** no exploitation reported by Ubiquiti or CISA as of 19 Nov 2026, and not in KEV at 05:40 GMT.
   We do not go further than that.
9. **"Auto-updated consoles may already be fixed"** is only a possibility. Automatic updates can be off, and users report
   rolling back from 4.3.24, so check every console.
10. **Console examples** (Cloud Key, UDM, UNVR) are not in the bulletin. The bulletin names the Access Application only;
    the checker works the same on any UniFi OS console.

## Checker: scripts/check-unifi-access.sh and scripts/Check-UnifiAccess.ps1

Both checkers are offline and read only. They never touch the network, never run UniFi or package tools, never write a
file and never print file contents, tokens or secrets: only version numbers, file paths and line numbers. They give the
same output for the same input (tested byte for byte).

```
bash scripts/check-unifi-access.sh --version 4.3.22
bash scripts/check-unifi-access.sh --file dpkg-l.txt --json apps.json --dir ./support-extracted
pwsh -File scripts/Check-UnifiAccess.ps1 -Version 4.3.9+12130 -Dir ./support-extracted
```

| Input | What it reads |
|---|---|
| `--version` / `-Version` | an Access Application version string, such as 4.3.22 or 4.3.9+12130 (the build suffix is ignored) |
| `--file` / `-File` | a saved text file: `dpkg -l` output, an application list or a log. JSON is detected automatically |
| `--json` / `-Json` | a saved JSON export of the applications list. Ubiquiti does not document the field names, so the checker looks for an Access entry under common name keys (name, id, key, app, displayName, packageName, title, slug) with a version key (version, currentVersion, installedVersion, appVersion). UNVERIFIED: if it finds none, the result is UNKNOWN |
| `--dir` / `-Dir` | an extracted support file folder (unpack it yourself first). Up to 2000 files, 8388608 bytes each, 12 levels deep. Symlinks are not followed; binary, unreadable and oversized files are skipped and reported |

The package name `unifi-access` in `dpkg -l` output is UNVERIFIED (Ubiquiti does not document it); the checker also
matches "UniFi Access Application" text. Each option is a separate source with its own verdict. If one source shows
both a fixed and an affected version (for example an old log line), the verdict is REVIEW. The worst source decides the
overall result.

| Exit | Meaning |
|---|---|
| 0 | FIXED: every source shows 4.3.24 or later |
| 2 | AFFECTED: a source shows a version below 4.3.24 (4.3.23 included) |
| 3 | UNKNOWN OR REVIEW: no version found, mixed versions in one source, or an incomplete scan |
| 5 | USAGE OR READ ERROR |

Exit 1 is not used by the checkers (reserved for unexpected runtime errors).

Where to get the inputs (manual steps, OUR STEPS):

- The Access Application version is shown in UniFi OS under the console's application and update settings; type it in
  with `--version`. Menu paths change between UniFi OS releases.
- Support file, as Ubiquiti staff describe it on the 4.3.24 release page: Site Manager > UniFi Console > Network >
  Settings > Management > General > Support File > Full > Download. Extract it and use `--dir`. Support files can hold
  configuration and secrets: keep them on a secured analyst machine and delete them when done.
- `dpkg -l` output only where you already have SSH to the console (SSH is off by default); save it and use `--file`.

## Hunts (all OUR PATTERN)

File: `kql/unifi-access-bulletin-073-hunting.kql`, for Microsoft Sentinel (Log Analytics). DeviceNetworkEvents also runs
in Defender advanced hunting. Tables: CommonSecurityLog, Syslog, DeviceNetworkEvents and a watchlist of console IPs.

Create a Sentinel watchlist named `UniFiConsoles` with each console IP as the SearchKey. Without one, replace the
watchlist line with an inline `datatable` as shown in the query header.

**Field names are UNVERIFIED for Access.** Ubiquiti's SIEM integration article documents CEF keys (UNIFIcategory,
UNIFIsubCategory, UNIFIadmin, UNIFIaccessMethod, UNIFIhost) for UniFi Network admin activity. It does not document Access
event text or keys. Q2 to Q5 therefore match keywords taken from the Alarm Manager article (door unlocked, unlock
schedule changed, lockdown mode changed, emergency mode updated, user or visitor added) and the Access API reference
(access.door.unlock, "Access Granted (Remote)"). Check them against a few real events before you rely on them.

| Query | Hunt | Table | MITRE ATT&CK |
|---|---|---|---|
| Q1 | UniFi admin activity, new admin and source pairs against a 14-day baseline | CommonSecurityLog | T1078 Valid Accounts, T1098 Account Manipulation |
| Q2 | Account, admin, role, API key and SSO changes (UNVERIFIED keywords) | CommonSecurityLog | T1136 Create Account, T1098 Account Manipulation |
| Q3 | Door policy, schedule, lockdown and emergency mode changes (UNVERIFIED keywords) | CommonSecurityLog | T1210 Exploitation of Remote Services |
| Q4 | Unlock events per hour, remote and out-of-hours unlocks marked (UNVERIFIED keywords) | CommonSecurityLog | T1210 Exploitation of Remote Services |
| Q5 | Q1 to Q4 in raw Syslog from UniFi senders | Syslog | T1078 Valid Accounts, T1098 Account Manipulation |
| Q6 | Internet traffic to console management ports (22, 443, 8443, 12442, 12443, 12445, 12478, 12812) | CommonSecurityLog | T1133 External Remote Services, T1190 Exploit Public-Facing Application |
| Q7 | Console outbound to new public destinations, unusual ports first | CommonSecurityLog | T1190 Exploit Public-Facing Application |
| Q8 | Endpoints connecting to consoles, new devices and command line tools marked | DeviceNetworkEvents | T1078 Valid Accounts, T1557 Adversary-in-the-Middle |

Ports are from Ubiquiti's Required Ports Reference: console GUI and API on TCP 443, SSH on 22 (only when enabled), the
Network application on 8443, and Access on 12442 (WebSocket), 12443 (HTTPS), 12445 (Open API), 12478 (TURN) and 12812
(MQTT). Remote management uses outbound 443, 8883 and 3478, so Q7 marks new destinations on those ports as REVIEW only.

## Sigma (all OUR PATTERN)

Nine rules in `sigma/`, date 2026-11-19, all passing `sigma check`. Kusto conversions for five pipelines are in
`sigma/converted/` (regenerate with `tests/sigma_convert.sh`).

| Rule | Matches KQL | Log source |
|---|---|---|
| unifi_cef_admin_activity | Q1 | product unifi, service cef (keywords) |
| unifi_cef_account_role_change | Q2 | product unifi, service cef (UNVERIFIED keywords) |
| unifi_cef_door_policy_lockdown_change | Q3 | product unifi, service cef (UNVERIFIED keywords) |
| unifi_cef_remote_unlock | Q4 | product unifi, service cef (UNVERIFIED keywords) |
| fw_unifi_access_ports_from_internet | Q6 | firewall |
| fw_unifi_console_management_from_internet | Q6 | firewall (replace the RFC 5737 example address 192.0.2.10 with your consoles) |
| fw_unifi_console_outbound_unusual_port | Q7 | firewall (same placeholder; no baseline, unlike Q7) |
| net_connection_win_script_to_unifi_access_api | Q8 | network_connection, windows |
| net_connection_lnx_script_to_unifi_access_api | Q8 | network_connection, linux |

28 conversions fail by design: the seven CEF and firewall rules have no table mapping in the microsoft_xdr,
microsoft_365_defender, sentinel_asim and azure_monitor pipelines (7 rules x 4 pipelines). Use the KQL for those, or
the no_pipeline output with your own table name. The two network_connection rules convert in every pipeline. They also
map to T1059 Command and Scripting Interpreter.

## OUR ADVICE (CybaVerse, not from Ubiquiti)

**Now:**

1. Inventory every UniFi OS console that runs UniFi Access Application, record the running Access version, and update
   anything below 4.3.24. Re-check after updating.
2. Keep UniFi OS and Access management off the internet: no port forwards to 443, 22, 8443 or the 124xx and 12812 Access
   ports. Use a management VLAN or VPN. Run Q6 to confirm.
3. Low-privilege accounts are enough for five of the seven CVEs. Remove shared, unused and stale local and cloud
   accounts, and enforce MFA on UI accounts.
4. Keep Access hubs, readers and intercoms on a segmented network.
5. Send UniFi CEF syslog to your SIEM if you do not already (Ubiquiti SIEM integration article), so Q1 to Q5 have data.

**Manual UniFi UI review checklist (OUR STEPS; menu names vary by version):**

- [ ] Admins: list every UniFi OS admin and its role. Remove anyone you do not recognise; check recent additions and role
      changes (owner, super admin, full and limited admins).
- [ ] Roles and Access account types: check Access roles and user account types (Admin, Basic, Role Based) for unexpected
      admin grants.
- [ ] SSO and identity: check SSO and directory sync settings and any recent changes.
- [ ] API tokens: Access > Settings > General > Advanced > API Token. Delete tokens you cannot explain; check scopes and
      expiry.
- [ ] Adopted devices: compare the Access device list (hubs, readers, intercoms) with what is installed. Re-adopt or
      remove anything you do not recognise (CVE-2026-132807 and CVE-2026-132808 involve adopted Access devices).
- [ ] Door policies and schedules: check access policies, unlock schedules, holiday schedules and any door set to stay
      unlocked.
- [ ] Lockdown and emergency settings: check lockdown and evacuation configuration and recent changes.
- [ ] Door logs: in the Access System Log, review the door_openings, admin_activity, critical, device_events, updates and
      visitor topics for the last 30 days, especially remote unlocks ("Access Granted (Remote)") and unlocks out of hours.
- [ ] Webhooks and Alarm Manager: check webhook endpoints and alarms for destinations you do not recognise.
- [ ] Export the logs and a support file before you change anything else.

**If you suspect compromise (OUR ADVICE): rotation and recovery checklist**

1. Export logs and a support file first; keep them as evidence.
2. Update UniFi Access Application to 4.3.24 or later (and UniFi OS to current).
3. Rotate UniFi admin passwords, UI account credentials and SSO secrets; revoke and recreate Access API tokens.
4. Remove unknown admins and users; review and re-adopt Access devices you cannot account for.
5. Restore door policies, schedules and lockdown settings from a known-good record.
6. Consider a factory reset and restore from a backup taken before the suspected compromise, then check the version again.
7. Check the console's outbound traffic (Q7) and the devices that managed it (Q8) for wider access.

## Testing

`tests/run_all.sh` runs everything: shellcheck, PSScriptAnalyzer, the bash tests and Pester tests (shared cases, parity
and edge trees), the static gates, the KQL parse, both checkers under bwrap with no network and a read-only filesystem,
`sigma check` and the conversions, the negative gates and a pack hash check.

## Sources

- Ubiquiti Security Advisory Bulletin 073: https://community.ui.com/releases/Security-Advisory-Bulletin-073/677d5551-5ad9-4c85-86e9-4cdd9636a1e2
- UniFi Access Application 4.3.24 release: https://community.ui.com/releases/UniFi-Access-Application-4-3-24/4b3b0ed1-ca11-478a-a1ca-1d215954e1d2
- UniFi SIEM integration (CEF): https://help.ui.com/hc/en-us/articles/33349041044119
- UniFi Alarm Manager: https://help.ui.com/hc/en-us/articles/27721287753239
- UniFi Required Ports Reference: https://help.ui.com/hc/en-us/articles/218506997
- UniFi Access API reference: https://assets.identity.ui.com/unifi-access/api_reference.pdf
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132802 (and CVE-2026-132803 to CVE-2026-132808)
- CVE records: https://www.cve.org/CVERecord?id=CVE-2026-132802 (and CVE-2026-132803 to CVE-2026-132808)
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Microsoft Learn tables: https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/commonsecuritylog, https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/syslog, https://learn.microsoft.com/en-us/defender-xdr/advanced-hunting-devicenetworkevents-table
- Microsoft Learn watchlists: https://learn.microsoft.com/en-us/azure/sentinel/watchlists-queries
- MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/ (and T1078, T1098, T1133, T1136, T1210, T1557, T1059)
