What is CVE-2026-94089?

CVE-2026-94089 is D-Link DIR-868L Authentication webfa_authentication.cgi strcpy stack-based overflow. The supplied enrichment data classifies it as Memory Corruption mapped to CWE-121 Stack-based Buffer Overflow; CWE-119 Improper Restriction of Operations within a Memory Buffer.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-94089. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-94089 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

2 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-94089 using CVSS 10, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalMemory Corruptionpublic exploit

CVE-2026-94089

CVE-2026-94089 — D-Link DIR-868L Authentication webfa_authentication.cgi strcpy stack-based overflow

A vulnerability was determined in D-Link DIR-868L 2.01b05. This issue affects the function strcpy of the file /webfa_authentication.cgi of the component Authentication Handler. Executing a manipulation of the argument id/password can lead to stack-based buffer overflow. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.

Published Sep 20, 2026Updated Sep 20, 2026Sources: NVD, D-Link (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

D-Link

DIR-868L

CVSS base

critical · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade DIR-868L to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.
Prioritize based on EPSS, PoC availability, and external exposure.
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
D-Link	DIR-868L	2.01b05	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

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
10	CVSS 3.1	critical	3.9	6	NVD, GHSA
10	CVSS 2.0	high	10	10	vuldb.com (CNA)
10	CVSS 4.0	critical	—	—	D-Link (CNA)
10	CVSS 3.1	critical	—	—	D-Link (CNA)
10	CVSS 3.0	critical	—	—	D-Link (CNA)
10	CVSS 2.0	critical	—	—	D-Link (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

Execute Unauthorized Code or Commands
Modify Memory
Read Memory
DoS: Crash, Exit, or Restart

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

CWE-121 · Stack-based Buffer Overflow

Modify Memory
DoS: Crash, Exit, or Restart
DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)

Mitigation: Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows. For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.

Weakness & attack patterns

CWE-121Stack-based Buffer Overflow
CWE-119Improper Restriction of Operations within a Memory Buffer

Inferred from the weakness class — not observed against this CVE.

CAPEC-100 · Overflow BuffersCAPEC-123 · Buffer Manipulation

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

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 /webfa_authentication.cgi, /password.
Prioritize edge telemetry for network-reachable DIR-868L.
Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

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 10.0 (AV:N)
Sep 20, 2026 · NVD
Initial · CVE published
Sep 20, 2026 · NVD
Reported · Advisory disclosed
Sep 20, 2026 · D-Link
Reported · VulDB entry created
Sep 20, 2026 · D-Link
Reported · VulDB entry last update
Sep 20, 2026 · D-Link
Added · GHSA-pc7v-4cmj-hg88 published (critical)
Sep 20, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 20, 2026 · SOCRadar CTI

References

8 on the record

github.com/Walnut1337/CVE/blob/main/poc/poc_crash.py
Exploit, Third Party Advisory
vuldb.com/cve/CVE-2026-94089
Vendor Advisory
vuldb.com/submit/951681
Vendor Advisory
vuldb.com/vuln/408017
Vendor Advisory
vuldb.com/vuln/408017/cti
Vendor Advisory
www.dlink.com/
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-94089
NVD
github.com/advisories/GHSA-pc7v-4cmj-hg88
Exploit, Third Party Advisory

Elsewhere on this site

D-Linkevery CVE for this vendor
Memory Corruptionsame 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-2026-94089 is D-Link DIR-868L Authentication webfa_authentication.cgi strcpy stack-based overflow, a critical vulnerability affecting DIR-868L from D-Link. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-94089. Public exploit evidence is: 2 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 10 describes technical severity, while EPSS 0% 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.