CVE-2021-27137
DD-WRT Stack-Based Buffer Overflow Vulnerability
An issue was discovered in router/upnp/src/ssdp.c in DD-WRT before 45724. An unsafe strcpy in the UPnP handling functionality allows an unauthenticated remote attacker to send a request that would overflow an internal fixed buffer. Exploitation requires the DD-WRT user to enable UPnP (which is off by default, and only listens on internal interfaces by default). This occurs in ssdp_msearch (reachable by an M-SEARCH request).
Published Updated Sources: NVD, DD-WRT (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Jul 21, 2026
EPSS
16%
ahead of 97% of scored CVEs
CVSS base
8.1
high
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade DD-WRT to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Federal deadline Jul 24, 2026 — passed 30 days ago
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| DD-WRT | DD-WRT | 0 to < 45724 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
High
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 8.1 | CVSS 3.1 | high | 2.2 | 5.9 | MITRE (CNA), DD-WRT (CNA), GHSA |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness & attack patterns
- CWE-121
Inferred from the weakness class — not observed against this CVE.
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Jul 21, 2026
Federal deadline
Jul 24, 2026
passed 30 days ago
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
10
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /upnp/src/ssdp.c.
- Prioritize edge telemetry for network-reachable DD-WRT.
- Monitor for scanner or exploit-pattern traffic after 10 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 8.1 (AV:N)
Jul 22, 2026 · NVD
Added to CISA KEV catalog
Jul 21, 2026 · CISA
Initial · CVE published
Jul 16, 2026 · NVD
Added · GHSA-qx3v-2jx6-8m2c published (high)
Jul 16, 2026 · GitHub Security Advisory
References
10 on the record
- securityaffairs.com/193290/uncategorized/iot-botnet-c0xmo-adds-competitor-killing-capability.html
Exploit, Third Party Advisory
- ssd-disclosure.com/ssd-advisory-dd-wrt-upnp-buffer-overflow/
Exploit, Third Party Advisory, Vendor Advisory
- svn.dd-wrt.com/changeset/45724
Patch, Vendor Advisory
- www.bleepingcomputer.com/news/security/c0xmo-botnet-spreads-via-dd-wrt-router-flaw-kills-rival-malware/
Exploit, Third Party Advisory, Vendor Advisory
- www.fortinet.com/blog/threat-research/inside-cross-platform-propagation-of-new-gafgyt-variant-c0xmo
Exploit
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-27137
US Government Resource
- nvd.nist.gov/vuln/detail/CVE-2021-27137
NVD, Vendor Advisory
- github.com/advisories/GHSA-qx3v-2jx6-8m2c
Exploit, Third Party Advisory
Elsewhere on this site
- DD-WRTevery CVE for this vendor
- July 2026what else CISA listed
- Remote Code Execsame class
- CWE-121other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2021-27137 is DD-WRT Stack-Based Buffer Overflow Vulnerability, a high vulnerability affecting DD-WRT from DD-WRT. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 10 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.1 describes technical severity, while EPSS 16% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.