LiveActive security incident?Get immediate response
CVE Record

CVE-2026-86297: D-Link DIR-605 L2TP Control Message tunnel.c tunnel_set_params off-by-one

A vulnerability was identified in D-Link DIR-605 B1v202WWB03. This issue affects the function tunnel_set_params of the file progs.gpl/pppd.alpha/l2tp/tunnel.c of the component L2TP Control Message Parser. Such manipulation of the argument peer_hostname  leads to off-by-one. The attack may be performed from remote. Attacks of this nature are highly complex. The exploitability is assessed as difficult. The exploit is publicly available and might be used.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A remotely reachable flaw in one specific D-Link DIR-605 hardware and firmware combination could let an attacker corrupt memory while the router processes L2TP control messages. Successful exploitation could compromise confidentiality, integrity, and availability. Exploitation is considered difficult, but public exploit material increases concern.

Executive priority

Treat as an immediate inventory and exposure-reduction priority because potential impact is severe and exploit information is public. Prioritize internet-reachable affected devices first. The high attack complexity reduces likelihood but does not offset the possible full compromise of a network-edge device.

Technical view

CVE-2026-86297 is an off-by-one, reported as an out-of-bounds write, in tunnel_set_params within the DIR-605 L2TP control-message parser. Manipulation of peer_hostname can trigger the flaw remotely without privileges or user interaction. CVSS 4.0 is 9.2, with high complexity and high device-level impacts.

Likely exposure

Exposure is limited by the available evidence to D-Link DIR-605 hardware running B1v202WWB03. Risk is greatest where the affected L2TP parser is reachable from untrusted networks. The sources do not establish whether other revisions, firmware versions, or products are affected.

Exploitation context

Public exploit information is referenced, and the CVSS vector marks proof-of-concept maturity. However, the CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation. Attack complexity is high and exploitability is assessed as difficult.

Researcher notes

The supplied evidence identifies peer_hostname processing in tunnel_set_params and classifies the defect under integer and off-by-one weaknesses. Public reporting describes an out-of-bounds write, but the bundle provides no vendor root-cause analysis, fixed version, indicators proving compromise, or confirmed exploitation campaign. Avoid extending the affected-version claim beyond B1v202WWB03.

Mitigation direction

  • Identify and prioritize DIR-605 devices running B1v202WWB03.
  • Restrict untrusted network access to L2TP services on affected devices.
  • Disable unnecessary L2TP functionality where operationally acceptable.
  • Isolate affected routers until authoritative remediation guidance is available.
  • Check D-Link guidance for supported firmware, mitigation, or replacement direction.

Validation and detection

  • Verify device model, hardware revision, and installed firmware against B1v202WWB03.
  • Determine whether L2TP is enabled and reachable from untrusted networks.
  • Review device logs and monitoring for unexpected restarts or abnormal L2TP activity.
  • Confirm compensating controls block unauthorized access to the L2TP service.
  • Recheck D-Link and CVE sources for newly published remediation guidance.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-189: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-193: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-86297 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (4.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——VulDB
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.25.9VulDB
8.1CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R2.25.9VulDB
7.6CVSS 2.0HighAV:N/AC:H/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:UR4.910VulDB

Vulnerability scoring details

Base CVSS 4.0 score

9.2Critical
CVSS 4.0 vector shape for CVE-2026-86297Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
D-LinkDIR-605B1v202WWB03Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-189 · source CWE mapping

Numeric Errors

Numeric Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-193 · source CWE mapping

Off-by-one Error

Off-by-one Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.