HIGH 8.1

CVE-2026-48610: UniFi OS Improper Access Control Vulnerability – CVSS 8.1 Analysis

A vulnerability in UniFi OS devices allows attackers on the network to make unauthorized changes to affected devices due to improper access controls. Under specific network configurations, an attacker doesn't need valid credentials to modify device settings—a significant risk for organizations relying on UniFi infrastructure for network management and security.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.1 HIGH · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-284
Affected products
0 configuration(s)
Published / Modified
2026-06-12 / 2026-06-17

NVD description (verbatim)

Under certain network configurations, a malicious actor with access to network could exploit an Improper Access Control vulnerability found in certain devices running UniFi OS to make unauthorized changes to such UniFi OS devices.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-48610 is an improper access control vulnerability (CWE-284) in UniFi OS that permits unauthenticated network-based exploitation under certain network configurations. The CVSS 3.1 score of 8.1 reflects a high-severity issue with high confidentiality, integrity, and availability impact, though exploitation requires specific network conditions (AC:H). The vulnerability allows threat actors to bypass authentication mechanisms and execute unauthorized administrative changes on affected UniFi OS devices.

Business impact

Organizations managing network infrastructure through UniFi OS devices face risk of unauthorized configuration changes that could result in network segmentation bypass, rogue access point creation, credential harvesting, or complete network compromise. The ability to modify device settings without authentication undermines the security posture of the entire managed network. In multi-tenant or critical infrastructure environments, this could lead to lateral movement, data exfiltration, or service disruption.

Affected systems

The vulnerability affects certain devices running UniFi OS. Specific product models and version ranges require verification against Ubiquiti's official security advisory. Organizations should cross-reference their UniFi device inventory against vendor-provided affected product lists to determine exposure scope. The vulnerability's manifestation depends on network configuration, meaning not all deployments are equally at risk.

Exploitability

Exploitation requires network access to the targeted UniFi OS device and relies on specific network configuration conditions, which elevates the technical bar somewhat. However, no authentication is required once an attacker reaches the network layer, making this exploitable by internal threats, compromised devices on the same network, or attackers who have already gained network proximity. The vulnerability is not believed to be actively exploited in the wild at this time, as it is not listed on the CISA Known Exploited Vulnerabilities catalog.

Remediation

Patch affected UniFi OS devices immediately by applying the security update released by Ubiquiti. Obtain the exact patched version numbers and timeline from Ubiquiti's security advisory. In the interim, network segmentation and access controls should restrict unauthorized devices from reaching UniFi management infrastructure. Disable remote management features if not actively required and implement network monitoring to detect suspicious administrative changes to UniFi devices.

Patch guidance

Check Ubiquiti's official security advisory for CVE-2026-48610 to identify the affected UniFi OS versions and corresponding patch versions. Deploy patches during a maintenance window, as updating UniFi OS typically requires device reboot. Verify patch application by confirming the running firmware version matches the recommended patched version provided by Ubiquiti. Test in a non-production environment first if feasible.

Detection guidance

Monitor for unusual administrative configuration changes on UniFi devices, particularly those made from unexpected source IP addresses or during off-hours. Review UniFi device logs for authentication bypass attempts or configuration change events lacking associated user credentials. Network intrusion detection systems should flag anomalous management traffic to UniFi devices from untrusted networks. Regular audit of device configurations against known-good baselines can reveal unauthorized modifications.

Why prioritize this

The CVSS 8.1 HIGH severity score, combined with the ability to make unauthorized administrative changes without authentication, warrants rapid prioritization. The impact scope includes integrity and confidentiality of the entire network managed by affected UniFi devices. While exploitation requires network access and specific configuration conditions, the barrier to entry is low once on the network, and the blast radius is substantial. Organizations should treat this as a priority patch.

Risk score, explained

The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) yields 8.1 due to network-based attack surface (AV:N), high impact across confidentiality, integrity, and availability (C:H/I:H/A:H), and no privilege or user interaction required (PR:N/UI:N). The attack complexity is rated HIGH (AC:H) because exploitation depends on specific network configuration conditions, preventing a critical score. However, the lack of any authentication requirement and direct network accessibility keep this in the HIGH tier.

Frequently asked questions

Do I need to be outside the network to exploit this vulnerability?

No. The vulnerability requires network-level access to the UniFi OS device, meaning the attacker must be on the network or have network connectivity to the device. This could be an internal threat, a compromised device on the same segment, or an attacker who has already achieved network proximity through other means. It is not a remote code execution vulnerability exploitable from the public internet unless the UniFi device is directly exposed.

How can I tell if my UniFi devices have been compromised by this vulnerability?

Review your UniFi device logs and configuration change history for entries without associated user credentials or from unusual source IPs. Check running firmware versions against the affected version list from Ubiquiti's advisory. Enable detailed logging on UniFi devices and monitor for spike in administrative events. If your configuration doesn't match your expected baseline, investigation is warranted.

Are all UniFi OS devices affected?

No. The vulnerability affects certain devices running UniFi OS under specific network configurations. Refer to Ubiquiti's official security advisory for the definitive list of affected product models and UniFi OS versions. Not every UniFi device or every network configuration is vulnerable, so verify your specific hardware and software combination against the vendor guidance.

What is the business risk if I delay patching?

Delaying patches exposes you to potential unauthorized modification of network infrastructure settings, which could allow attackers to pivot laterally, establish persistence, steal credentials, or disrupt services. In regulated environments, known unpatched vulnerabilities may trigger compliance violations. The longer the exposure window, the greater the window for opportunistic exploitation by insiders or network-based threats.

This analysis is based on publicly available information current as of the publication date. Specific affected product models, patch versions, and deployment guidance must be verified against Ubiquiti's official security advisory. No exploit code, proof-of-concept, or detailed attack steps are provided. Organizations should conduct their own risk assessment and testing before applying patches in production environments. This information is provided for educational and defensive security purposes only. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).