CVE-2025-34037Known exploitationPublic exploitNetwork attack vector

Unauthenticated command execution via unsanitized ttcp_ip

Published Jun 24, 2025 · Updated Jul 22, 2026

OS command injection in Linksys E-Series router firmware allows remote attackers to execute arbitrary commands through an unauthenticated HTTP request. The tmUnblock.cgi and hndUnblock.cgi handlers pass the unsanitized ttcp_ip value into a shell command, so backticks execute attacker-supplied text. Exposure requires reachable HTTP management on port 8080; successful commands run on the router and have been used to install a MIPS worm payload.

CVSS severity10.0
Critical
EPSS probability90.94%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

OS command injection in Linksys E-Series router firmware allows remote attackers to execute arbitrary commands through an unauthenticated HTTP request. The tmUnblock.cgi and hndUnblock.cgi handlers pass the unsanitized ttcp_ip value into a shell command, so backticks execute attacker-supplied text. Exposure requires reachable HTTP management on port 8080; successful commands run on the router and have been used to install a MIPS worm payload.

The record

CVE
CVE-2025-34037
Published
Jun 24, 2025
Updated
Jul 22, 2026
Vendor
Linksys
Product
Linksys E4200
Classifications
CWE-20, CWE-78, CAPEC-88, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 13, 2014Exploitation reportedTheMoon worm exploitation of Linksys E-Series routers
  2. Feb 6, 2025Exploitation reportedShadowserver exploitation observation
  3. Jun 24, 2025CVE publishedPublication date reported by the CVE source.
  4. Jul 22, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.0.06

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Linksys · Linksys E4200version=0 <1.0.06
Linksys · Linksys E3200version=0 <1.0.05
Linksys · Linksys E2000version=0
Linksys · Linksys E1000version=0 <2.1.03
Linksys · Linksys E900version=0 <1.0.04
Linksys · Linksys E1200version=0 <=1.0.04
Linksys · Linksys E2100Lversion=0 <=1.0.05
Linksys · Linksys E1550version=0 <=1.0.03
Linksys · Linksys E1500version=0 <1.0.06
Linksys · Linksys E3000version=0 <1.0.06
Linksys · Linksys E2500version=0 <2.0.00

Published CVSS scores

10.0VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-20Improper Input Validation
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CAPEC-88OS Command Injection
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo