# CVE-2026-77532: Memory corruption in EdgeMAX EdgeSwitch

> A remote attacker on an adjacent network can achieve code execution on Ubiquiti EdgeMAX EdgeSwitch devices via a buffer overflow in DHCPv6.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-ff9h-mmj4-g6xx

## What is CVE-2026-77532?

CVE-2026-77532 is a high-severity memory corruption vulnerability in Ubiquiti Inc EdgeMAX EdgeSwitch, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A malicious actor with access to an adjacent network could exploit a Buffer Overflow vulnerability found in a DHCPv6-enabled EdgeMAX EdgeSwitch to initiate a Remote Code Execution on such device.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-77532?


## How do I fix CVE-2026-77532?

No fix has been published for CVE-2026-77532 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77532 being exploited?

There is no known exploitation of CVE-2026-77532 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77532 and fix it if it is affected.

What it is: CVE-2026-77532 is a high-severity memory corruption vulnerability in Ubiquiti Inc EdgeMAX EdgeSwitch, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77532 in the wild and no public exploit code.

Affected product: Ubiquiti Inc EdgeMAX EdgeSwitch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77532/ (Markdown: https://insights.sbomify.com/CVE-2026-77532/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77532
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77532
- OSV: https://osv.dev/vulnerability/CVE-2026-77532

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77532/
Summaries are generated and may contain mistakes; the official description above is the record.