An Improper Certificate Validation on the UniFi iOS App managing a standalone UniFi Access Point (not using UniFi Network Application) could allow a malicious actor with access to an adjacent network to take control of this UniFi Access Point.
Affected Products: UniFi iOS App (Version 10.17.7 and earlier) Mitigation: UniFi iOS App (Version 10.18.0 or later).
Ubiquiti UniFi 52 devices, when Hotspot mode is used, allow remote attackers to bypass intended restrictions on "free time" Wi-Fi usage by sending a /guest/s/default/ request to obtain a cookie, and then using this cookie in a /guest/s/default/login request with the byfree parameter.
UniFi iOS app 10.15.0 introduces a misconfiguration on 2nd Generation UniFi Access Points configured as standalone (not using UniFi Network Application) that could cause the SSID name to change and/or the WiFi Password to be removed on the 5GHz Radio.
This vulnerability is fixed in UniFi iOS app 10.15.2 and later.
UniFi: 10.0 NVD - CVE-2026-22557 ScreenConnect: 9.0 NVD - CVE-2026-3564
Nobody has said it yet (not that I've heard), but this would be how I assume adversarial AI systems enter the arena. Hopefully these were security researchers using tools to bug hunt & claim bounties, but two major players in the same week - makes me wonder.
As I've been telling friends and clients, the rate of small intrusion to network takeover is accelerating. The window to respond is closing. Historically, a foothold gave enough time to detect, triage, & remediate, at attack team/human operation cycles. Humans vs humans, you've got (some) time.
My hypothesis/assumption here, but that rate is probably thrown out the window. A small breach + rapidly iterating attacks against all internal services will turn up the next weakness in the chain, until full access is accomplished.
These AI systems are like a 50-Cal Rifle, you use them to punch a hole into the network, and the attack pours through that hole.
For defenders, you can't be constantly on guard, can't be constantly ready to "fire back" or deploy time/energy chasing down everything that makes the system throw an alert.
Maybe I'm just a bit burned out, but two days in a row my evenings have gone to shit, as I'm digging through logs and reading up on the next problem to tackle tomorrow - and meanwhile keeping clients advised of what's going on, and still trying to leverage remote support via tools that are BROKEN because of the PATCH - effing ScreenConnect - no notice no comms - not a care in the world to share it with PAYING CUSTOMERS.