Edge exposure D-Link / L2TP
D-Link DIR-895L: check the L2TP exposure, then plan its replacement
The important detail in CVE-2026-100740 is the router's role in the tunnel. The disclosed path involves an L2TP WAN connection and a malicious upstream peer. For owners of this unsupported router, configuration review and replacement planning belong on the same ticket.
An internet-facing router is not necessarily exposing every parser it contains. Here, the original research describes the DIR-895L processing control messages from an upstream L2TP peer. That distinction changes which settings an administrator should check first. Researcher disclosure
01 / Follow the configured path
The upstream peer supplies the input
The CVE record identifies firmware A1_102b07 and an out-of-bounds write in tunnel_set_params. The research traces it to the handling of a Host Name field in L2TP control traffic: a string terminator is written beyond the hostname buffer. Reported consequences include tunnel instability, crashes, and corruption of the tunnel object. CVE record · Technical disclosure
- 01 / Peer
Malicious or impersonated server
The attacker controls the peer or can spoof or intercept it.
- 02 / Input
L2TP control message
The Host Name field reaches the configured WAN client's parser.
- 03 / Fault
Write outside the buffer
The disclosure reports memory corruption and tunnel instability.
This is not a demonstrated internet-to-root takeover. The original disclosure does not establish root-level code execution, and the CNA's severity vectors specify low privileges rather than no privileges. The useful exposure test is the documented WAN configuration and peer relationship, not a generic open-port count.
Record details and exploitation status
- Affected version listed
- DIR-895L
A1_102b07. The record does not establish that other installed builds are safe. - Severity
- VulDB, the CNA: CVSS 3.1 9.9 and CVSS 4.0 9.4. Both vectors include
PR:L. - Public material
- The record says an exploit is public. The original disclosure provides a PoC outline, not a demonstrated root exploit.
- KEV check
- Not listed in the retrieved official CISA catalog, version 2026.09.25, checked September 27. This is not evidence that exploitation is absent.
02 / Similar names, different roles
Do not confuse the WAN client with the VPN server
Path described in the research
L2TP WAN connection
The router connects to its provider's tunnel server. Check the Internet/WAN connection type and configured peer.
This is where the exposure review starts.
Separate product feature
Quick VPN remote access
D-Link also documents an L2TP-over-IPsec server for remote users. Its presence alone does not establish this vulnerability's reachability.
Review it separately. Do not equate the two.
D-Link's manuals describe both roles. Disabling Quick VPN or web remote management is therefore not, by itself, evidence that the disclosed WAN path has been removed. Changing the WAN connection type can also take the site offline. Confirm the provider's requirements before making that change. WAN settings, manual page 74 · Quick VPN, manual page 172
03 / Give the owner a concrete task
Build the replacement plan while checking exposure
D-Link identifies the DIR-895L/R family as end of life and recommends retirement. Its lifecycle advisory says firmware development has ceased. No fixed firmware is identified in the reviewed CVE record or original disclosure. An old download remaining on a support page is not a fix for this issue. D-Link lifecycle advisory
- Output: configuration-backed inventory
Confirm what is installed
Record the hardware revision, firmware, WAN mode, peer address, and owner. Include remote access and the networks behind the device. A model name in an asset list will not answer the connection question.
- Output: approved change and rollback plan
Reduce exposure without breaking the site
Disable unnecessary services. Where supported, restrict tunnel communication to approved peers as an interim measure. If L2TP supplies the site's internet connection, agree an alternative with the provider before disabling it.
- Output: supported device and checked configuration
Replace it and verify the result
Assign an owner and date for a supported replacement. Protect the configuration export, rebuild only the required rules, and test connectivity, remote administration, segmentation, and log delivery after the cutover.
04 / Retain evidence the router may lose
Watch the tunnel, not just the admin login
For an affected L2TP WAN deployment, retain peer changes, tunnel failures, restarts, and relevant network records where available. Compare them with provider maintenance and authorized changes. A restart is a reason to investigate, not a signature for this CVE.
If the router appears compromised, preserve available logs and a protected configuration copy before a reset. Review administrative users, DNS settings, routes, and remote-access rules against the approved configuration. Coordinate isolation with the service owner.
For deception coverage, the same distinction applies: a router-looking login page does not observe an L2TP control parser. A decoy should be tested against the protocol behavior it claims to monitor, with a recorded interaction and a verified alert path.
The exposure decision needs the WAN configuration. The replacement decision already has the vendor's answer.
Sources and review
- CVE Program record: affected version, CNA severity, and disclosure references.
- Original researcher disclosure: WAN configuration, upstream-peer conditions, and reported effects.
- D-Link SAP10299: lifecycle and replacement guidance. This is a family-level advisory, not confirmation of a fix for CVE-2026-100740.
Reviewed September 27, 2026. The operational checklist is our analysis. No Deception Check fleet observations are presented as evidence of this vulnerability.