CVE-2026-2151VulnerabilityPublished 8 Feb 2026Updated 23 Feb 2026

CVE-2026-2151: D-Link DIR-615 · OS Command Injection

Affects D-Link DIR-615Source CVE Database V5

Not known to be exploited · CVSS 8.6 High · end of life, no fix coming : replace or isolate D-Link DIR-615; no fix will be released.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 5.3% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

No fix will be released: D-Link DIR-615 is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
D-LinkDIR-615	Affected =4.10	Fixed in–

AI-suggested

Given the absence of official patches due to end-of-life status, organizations should prioritize replacing affected D-Link DIR-615 devices with supported hardware that receives regular security updates. In the interim, network administrators should restrict access to the router's management interface, limiting it to trusted internal networks and using strong authentication mechanisms. Disabling the DMZ Host feature entirely can mitigate the attack vector. Network segmentation should be enforced to isolate vulnerable devices from critical assets. Monitoring network traffic for unusual activity and employing intrusion detection systems can help detect exploitation attempts. If replacement is not immediately feasible, consider deploying firewall rules to block external access to the router's management ports and regularly audit device configurations. Additionally, educating users about the risks of using unsupported hardware is essential.

Description

A vulnerability has been found in D-Link DIR-615 4.10. This affects an unknown part of the file adv_firewall.php of the component DMZ Host Feature. Such manipulation of the argument dmz_ipaddr leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Impact

The impact of CVE-2026-2151 is significant for organizations using the affected D-Link DIR-615 routers. Successful exploitation could lead to full compromise of the router, allowing attackers to execute arbitrary commands with high privileges. This can result in unauthorized access to internal networks, interception or modification of network traffic, disruption of network availability, and potential lateral movement to other systems. Since the device is a network gateway, compromise could undermine the security posture of the entire network. The lack of vendor support and patches increases the risk, as organizations cannot remediate via firmware updates. This vulnerability could be exploited in targeted attacks against enterprises, small businesses, or home users relying on these routers, especially in environments where network segmentation is weak. The public disclosure may lead to the development of automated exploit tools, increasing the threat landscape.

Summary

CVE-2026-2151 is an OS command injection vulnerability identified in the D-Link DIR-615 router firmware version 4.10, specifically within the adv_firewall.php script that handles the DMZ Host feature. The vulnerability arises from insufficient validation or sanitization of the dmz_ipaddr parameter, which an attacker can manipulate to inject arbitrary operating system commands. This flaw allows remote attackers to execute commands on the underlying system with high privileges, potentially leading to full device compromise. The attack vector is network-based, requiring no user interaction, but does require authentication with high privileges, possibly administrative access to the device's web interface. The vulnerability affects only devices that are no longer supported by D-Link, meaning no official patches or firmware updates are available. Although no known exploits have been observed in the wild, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The CVSS v4.0 score of 8.6 reflects the high impact on confidentiality, integrity, and availability, combined with the ease of exploitation once authenticated. This vulnerability could allow attackers to manipulate firewall settings, intercept or redirect traffic, or use the compromised router as a foothold for further network attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:36 UTC

Technical details

References

Community reviews

Related threats