# CVE-2026-9032: Unauthenticated Onboarding Connect NULL Pointer Dereference Denial of Service Vulnerability in TP-Link Tapo C120 & C200

> An unauthenticated attacker on the local network can crash the HTTPS service of TP-Link Tapo cameras by sending a malformed onboarding request.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 1 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-gq3v-7fcg-vgjc

## What is CVE-2026-9032?

CVE-2026-9032 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C120 V1, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tapo C120 v1 and C200 v5
contain a NULL pointer dereference in the HTTPS onboarding connect request parser.  The interface is reachable without
authentication after initial setup and does not validate that a password field
is present for certain authentication and encryption parameter combinations,
allowing a malformed request from the same local network to crash the HTTPS service

 Successful exploitation may
temporarily make HTTPS management functions unavailable. Repeated malformed
requests may sustain the denial-of-service condition, and recovery may in some
cases require a device reboot.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2026-9032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9032 is a high-severity vulnerability in TP-Link Systems Inc. Tapo C120 V1, published on 1 Oct 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-9032 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Tapo C120 V1. 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-9032/ (Markdown: https://insights.sbomify.com/CVE-2026-9032/index.md)
```

## Sources

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

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