Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2927: Stack-based Buffer Overflow in D-Link DWR-M960

0
High
VulnerabilityCVE-2026-2927cvecve-2026-2927
Published: Sun Feb 22 2026 (02/22/2026, 04:32:15 UTC)
Source: CVE Database V5
Vendor/Project: D-Link
Product: DWR-M960

Description

CVE-2026-2927 is a high-severity stack-based buffer overflow vulnerability in the D-Link DWR-M960 router firmware version 1. 01. 07. It exists in the Operation Mode Configuration Endpoint, specifically in the function sub_462590 handling the submit-url argument. This vulnerability can be exploited remotely without authentication or user interaction, allowing attackers to execute arbitrary code with elevated privileges. The vulnerability has a CVSS 4. 0 score of 8. 7, indicating a significant risk to confidentiality, integrity, and availability. Although no public exploits are currently known in the wild, the exploit details have been disclosed publicly. Organizations using this router model are at risk of compromise, including potential full device takeover.

AI-Powered Analysis

AILast updated: 02/22/2026, 05:01:29 UTC

Technical Analysis

CVE-2026-2927 is a stack-based buffer overflow vulnerability identified in the D-Link DWR-M960 router firmware version 1.01.07. The flaw resides in the Operation Mode Configuration Endpoint, specifically within the function sub_462590 that processes the submit-url parameter. An attacker can remotely send a specially crafted request manipulating this argument to overflow the stack buffer, potentially overwriting the return address or other control data on the stack. This can lead to arbitrary code execution with elevated privileges on the device, compromising its confidentiality, integrity, and availability. The vulnerability requires no authentication or user interaction, making it highly exploitable over the network. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low complexity, no user interaction, and partial remediation effectiveness. Although no known exploits are currently active in the wild, the public disclosure of exploit details increases the risk of imminent attacks. The affected device is a widely deployed 4G LTE router used in various enterprise and consumer environments, making this vulnerability a critical concern for network security.

Potential Impact

The exploitation of CVE-2026-2927 can have severe consequences for organizations worldwide. Successful attacks can lead to full compromise of the affected router, allowing attackers to execute arbitrary code, potentially gaining persistent control over the device. This can result in interception or manipulation of network traffic, disruption of internet connectivity, and use of the device as a pivot point for further attacks within the internal network. Confidential data passing through the router may be exposed or altered, and the integrity of network operations can be undermined. Given the router’s role in providing critical connectivity, availability may also be impacted through denial-of-service conditions caused by exploitation. Organizations relying on D-Link DWR-M960 routers in enterprise, industrial, or critical infrastructure contexts face heightened risks of espionage, sabotage, or ransomware attacks leveraging this vulnerability.

Mitigation Recommendations

To mitigate CVE-2026-2927, organizations should immediately verify if they are using the D-Link DWR-M960 router with firmware version 1.01.07. If so, they should seek and apply any official firmware updates or patches released by D-Link addressing this vulnerability. In the absence of an official patch, network administrators should restrict access to the router’s management interfaces by implementing network segmentation and firewall rules to limit exposure to trusted IP addresses only. Disabling remote management features or changing default management ports can reduce attack surface. Monitoring network traffic for anomalous requests targeting the /boafrm/formOpMode endpoint and the submit-url parameter can help detect exploitation attempts. Employing intrusion detection/prevention systems (IDS/IPS) with signatures for this vulnerability is recommended. Regularly auditing router configurations and maintaining up-to-date inventories of network devices will aid in rapid response. Finally, organizations should consider replacing affected devices with models that have robust security track records if patches are unavailable or delayed.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-21T04:58:33.810Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699a8a51be58cf853bdd6463

Added to database: 2/22/2026, 4:47:13 AM

Last enriched: 2/22/2026, 5:01:29 AM

Last updated: 2/22/2026, 7:22:23 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats