airMAX M: Heap-based Buffer Overflow
CVE-2026-116837 is a high-severity heap-based buffer overflow vulnerability in airMAX M from Ubiquiti, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 6.3.26 as the first without the flaw, so updating airMAX M to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update airMAX M to 6.3.26 or a later version.
- Update LTU PTMP to 2.4.2 or a later version.
- Update LTU PTP to 1.5.7 or a later version.
- Read the advisory on uisp.community.ui.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Ubiquiti | airMAX M | before 6.3.26 | 6.3.26 |
| Ubiquiti | LTU PTMP | before 2.4.2 | 2.4.2 |
| Ubiquiti | LTU PTP | before 1.5.7 | 1.5.7 |
| Ubiquiti | SolarPoint / SolarSwitch | before 2.0.3 | 2.0.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
A malicious actor with access to the adjacent network could exploit a Heap-based Buffer Overflow vulnerability found in airMAX M, LTU, SolarPoint, and SolarSwitch devices to execute arbitrary code on the device.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in airMAX M
- 7.1 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 8.8 High severity
- 9.3 Critical severity
- 7.7 High severity
- 9.2 Critical severity
- 9.2 Critical severity
- 9.4 Critical severity
Spotted an error? Tell us.