cve.bz

CVE-2026-9032 tp-link systems inc.: NULL Pointer Dereference

7.1 highEPSS 0.2%

High (7.1) in tp-link systems inc.. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.1 high
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
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-9032 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-9032?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-9032?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-9032 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • tp-link systems inc.:tapo c120 v1
  • tp-link systems inc.:tapo c200 v5

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Tapo C200 V5before V5_1.4.6 Build 260709 Rel.27675n
TP-Link Systems Inc. Tapo C120 V1before V1_1.9.4 Build 260813 Rel.79754n

References

Check your stackJSON