CVE-2026-75489 Cudy TR3000 before 2.5.42 SMT Message Forgery via Probe Request Vendor IE

6.1 mediumEPSS 0.2%

Medium (6.1) in shenzhen cudy technology co., ltd. tr3000 1.0. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Affected
Versions
Attack patterns (CAPEC)
References
Your exposure

Cudy TR3000 before 2.5.42 contains an insufficient verification of data authenticity vulnerability in the mt_wifi Smart Mesh Technology (SMT) onboarding, which protects messages only with an AES-CBC key derived from public values and a CRC32 check. Adjacent unauthenticated attackers can forge SMT messages in Probe Request vendor IEs carrying an attacker-chosen SSID and pre-shared key, forcing unpaired devices to join attacker-controlled access points.

Severity

CVSS 4.0

6.1 medium

CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.8 medium

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS: 0.2% estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-13. 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-11-13. 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-345 Insufficient Verification of Data Authenticity
OWASP Top 10: A08:2025 Software or Data Integrity Failures
Published: 2026-11-13 10:18 UTC
Modified: 2026-11-13 16:19 UTC
Assigned by: VulnCheck (CNA)
NVD analysis: Awaiting analysis
Record from: the NVD, synced 2026-11-13 16:40 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-75489 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-75489?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-75489?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-75489 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.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-75489](https://cve.bz/cve/badge/CVE-2026-75489.svg)](https://cve.bz/cve/CVE-2026-75489)

HTML:

<a href="https://cve.bz/cve/CVE-2026-75489"><img src="https://cve.bz/cve/badge/CVE-2026-75489.svg" alt="CVE-2026-75489"></a>

Affected

shenzhen cudy technology co., ltd.:tr3000 1.0

Versions

From the CNA's record in the CVE List.

Product	Affected
Shenzhen Cudy Technology Co., Ltd. TR3000 1.0	before 2.5.42

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stack JSON