CVE
Shenzhen Cudy TR3000 denial of service in stun_client UDP parser
Only affects Cudy TR3000 1.0 firmware before 2.5.42 where the stun_client TR-111 UDP Connection Request parser is reachable. Fixed in 2.5.42.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.42
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.5.42.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 1.18% · 68th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Cudy TR3000 routers before version 2.5.42 have a flaw in the stun_client UDP parser that allows a stack buffer overflow. A remote attacker can exploit it without logging in by sending a single crafted UDP packet, which crashes stun_client and causes a denial of service.
Original description
Cudy TR3000 before 2.5.42 contains an unauthenticated stack buffer overflow vulnerability in the stun_client TR-111 UDP Connection Request parser that parses requests before verifying username or HMAC. Remote attackers can send a single crafted UDP datagram lacking a space in the request line, causing strncpy() to overflow a 10-byte stack buffer and crash stun_client for denial of service.
Who should check
Teams running Cudy TR3000 routers with firmware before 2.5.42
“Affecting TR3000 1.0 >= 0, < 2.5.42”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.5.42.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-75492 (Cudy TR3000 before 2.5.42 Stack Buffer Overflow via stun_client UDP Parser), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-75492 (entry last updated 2026-11-13):
Affected:
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0: fixed in 2.5.42
Fixed versions: 2.5.42.
Conditions (all must be true for the bug to be hit):
- Cudy TR3000 firmware before 2.5.42 (source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-stack-buffer-overflow-via-stun-client-udp-parser)
- The stun_client TR-111 UDP Connection Request parser must be reachable (source: https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-stack-buffer-overflow-via-stun-client-udp-parser)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-75492 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75492 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://d1jvyy13vm72kv.cloudfront.net/device/upgrade/m_upgrade_TR3000_256MB_Flash-R103-2.5.42-20261103-160202-sysupgrade_82672.zip
- https://www.cudy.com/en-us/pages/download-center/tr3000-1-0
- https://www.vulncheck.com/advisories/cudy-tr3000-before-2.5.42-stack-buffer-overflow-via-stun-client-udp-parser
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-75492
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75492"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Shenzhen Cudy Technology Co., Ltd. TR3000 1.0
fixed in 2.5.42
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-75492
Is CVE-2026-75492 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A stack buffer overflow in the stun_client TR-111 UDP Connection Request parser can crash stun_client, causing a denial of service.Source: vulncheck.com
Which versions are affected by CVE-2026-75492?
TR3000 1.0: before 2.5.42.Source: cve.now feed data
Am I affected, and how do I check?
TR3000 1.0 firmware before 2.5.42 is affected, but only where the stun_client TR-111 UDP Connection Request parser is reachable. Compare the installed firmware version with 2.5.42 to check the version side.Source: vulncheck.com
How do I fix CVE-2026-75492?
Upgrade to firmware 2.5.42, the version listed as the fix.Source: vulncheck.com