Skip to content
Fencer Intel
high 8.1

CVE-2026-48610 json

Under certain network configurations, a malicious actor with access to network could exploit an Improper Access Control vulnerability found…

published 5mo ago modified 4mo ago also EUVD-2026-36378

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

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.

Patch / fix

  • Ubiquiti Inc UDM 5.1.15
  • Ubiquiti Inc UDM-Pro 5.1.15
  • Ubiquiti Inc UDM-SE 5.1.15
  • Ubiquiti Inc UDM-Pro-Max 5.1.15
  • Ubiquiti Inc UDM-Beast 5.1.15
  • Ubiquiti Inc EFG 5.1.15
  • Ubiquiti Inc UDW 5.1.15
  • Ubiquiti Inc UDR 5.1.15
  • Ubiquiti Inc UDR7 5.1.15
  • Ubiquiti Inc UDR-5G 5.1.15
  • Ubiquiti Inc Express 7 5.1.15
  • Ubiquiti Inc UCG-Ultra 5.1.15
  • Ubiquiti Inc UCG-Max 5.1.15
  • Ubiquiti Inc UCG-Fiber 5.1.15
  • Ubiquiti Inc UCG-Industrial 5.1.15

Is CVE-2026-48610 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
4mo ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Ubiquiti Inc UDM
  • Ubiquiti Inc UDM-Pro
  • Ubiquiti Inc UDM-SE
  • Ubiquiti Inc UDM-Pro-Max
  • Ubiquiti Inc UDM-Beast
  • Ubiquiti Inc EFG
  • Ubiquiti Inc UDW
  • Ubiquiti Inc UDR
  • Ubiquiti Inc UDR7
  • Ubiquiti Inc UDR-5G
  • Ubiquiti Inc Express 7
  • Ubiquiti Inc UCG-Ultra
  • Ubiquiti Inc UCG-Max
  • Ubiquiti Inc UCG-Fiber
  • Ubiquiti Inc UCG-Industrial

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.