How severe is CVE-2026-104944?

CVE-2026-104944 has a CVSS 4.0 base score of 7.1, rated high severity.

Is CVE-2026-104944 being actively exploited?

It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.

How do I fix CVE-2026-104944?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-104944 published?

CVE-2026-104944 was published on 2026-10-06.

CVE-2026-104944

CVE-2026-104944 is a high-severity vulnerability with a CVSS 4.0 base score of 7.1. The underlying weakness is classified as CWE-823.

Key facts

Severity: High (CVSS 4.0 base score 7.1)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-823
Published: 2026-10-06
Last modified: 2026-10-06

Description

TP-Link Tapo C500 v2.0 contains an out-of-bounds function-pointer dispatch in its TDP (TP-Link Device Protocol) daemon. A single unauthenticated UDP datagram can cause an invalid indirect call, crashing the main service and resulting in a denial-of-service condition. Successful exploitation may allow an unauthenticated attacker with network access to the affected UDP service to repeatedly crash the TDP daemon, disrupting normal device operation and availability. No authentication, session establishment, or pairing is required to trigger the condition.

Frequently asked questions

What is CVE-2026-104944?: TP-Link Tapo C500 v2.0 contains an out-of-bounds function-pointer dispatch in its TDP (TP-Link Device Protocol) daemon. A single unauthenticated UDP datagram can cause an invalid indirect call, crashing the main service and resulting in a denial-of-service condition. Successful exploitation may allow an unauthenticated attacker with network access to the affected UDP service to repeatedly crash the TDP daemon, disrupting normal device operation and availability. No authentication, session establishment, or pairing is required to trigger the condition.
How severe is CVE-2026-104944?: CVE-2026-104944 has a CVSS 4.0 base score of 7.1, rated high severity.
Is CVE-2026-104944 being actively exploited?: It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.
How do I fix CVE-2026-104944?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-104944 published?: CVE-2026-104944 was published on 2026-10-06.

References

Other CWE-823 vulnerabilities

CVE-2023-43553 — Critical (CVSS 9.8): Memory corruption while parsing beacon/probe response frame when AP sends more supported links in MLIE.
CVE-2026-46244 — Critical (CVSS 9.1): In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_inner: Fix IPv6 inner_thoff…
CVE-2026-72642 — High (CVSS 8.8): The native inference process that Elasticsearch uses to evaluate uploaded machine learning models accepts a model…
CVE-2025-27059 — High (CVSS 8.8): Memory corruption while performing SCM call.
CVE-2022-0729 — High (CVSS 8.8): Use of Out-of-range Pointer Offset in GitHub repository vim/vim prior to 8.2.4440.
CVE-2017-20211 — High (CVSS 8.6): UCanCode E-XD++ Visualization Enterprise Suite contains an untrusted pointer dereference vulnerability via the…

Browse all CWE-823 vulnerabilities →