CVE-2026-94036
CVE-2026-94036 — D-Link DIR-X1860/DIR-X1860Z routerd ubus access control
A security flaw has been discovered in D-Link DIR-X1860 and DIR-X1860Z up to 1.0.2.220120.165402. The impacted element is an unknown function of the file /ubus of the component routerd. The manipulation of the argument passwd_set results in improper access controls. The attack must originate from the local network. The exploit has been released to the public and may be used for attacks.
Published Updated Sources: NVD, D-Link (CNA), GitHub, 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
0%
ahead of 0% of scored CVEs
CVSS base
8.8
high · 6 sources
Remediation
The vendor's own words where we have them.
Upgrade DIR-X1860 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-X1860 | 1.0.2.220120.165402 | Vulnerable |
| D-Link | DIR-X1860Z | 1.0.2.220120.165402 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
High
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Adjacent
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 |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | high | 2.8 | 5.9 | NVD |
| 8.3 | CVSS 2.0 | high | 6.5 | 10 | vuldb.com (CNA) |
| 8.7 | CVSS 4.0 | high | — | — | D-Link (CNA) |
| 8.8 | CVSS 3.1 | high | — | — | D-Link (CNA) |
| 8.8 | CVSS 3.0 | high | — | — | D-Link (CNA) |
| 8.3 | CVSS 2.0 | high | — | — | D-Link (CNA) |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/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.
CWE-266 · Incorrect Privilege Assignment
- Gain Privileges or Assume Identity
Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
CWE-284 · Improper Access Control
- Varies by Context::
Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Weakness & attack patterns
- CWE-284Improper Access Control
- CWE-266
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1027.009Obfuscated Files or Information: Embedded Payloads
- T1546.004Event Triggered Execution: .bash_profile and .bashrc
- T1546.016Event Triggered Execution: Installer Packages
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Social mentions
Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.
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 /ubus.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
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 8.8 (AV:A)
Sep 20, 2026 · NVD
Initial · CVE published
Sep 20, 2026 · NVD
Reported · VulDB entry last update
Sep 20, 2026 · D-Link
CVE published by MITRE.
Sep 20, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Sep 19, 2026 · D-Link
Reported · VulDB entry created
Sep 19, 2026 · D-Link
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×Tweets · 1 time tweeted.Sep 20, 2026 · SOCRadar CTI
- 1×1 time mentioned on 1 Telegram channelSep 20, 2026 · SOCRadar CTI
- 1×SVRS is calculatedSep 20, 2026 · SOCRadar CTI
- 1×Github_Repos · Github repository created, djzzlim/CVE-2026-94036Sep 19, 2026 · SOCRadar CTI
References
7 on the record
- pastebin.com/gzKNCCPV
Vendor Advisory
- supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10513
Vendor Advisory
- vuldb.com/cve/CVE-2026-94036
Vendor Advisory
- vuldb.com/submit/947565
Vendor Advisory
- vuldb.com/vuln/407965
Vendor Advisory
- vuldb.com/vuln/407965/cti
Vendor Advisory
- www.dlink.com/
Vendor Advisory
Coverage
1 story from the feeds we poll
Elsewhere on this site
- D-Linkevery CVE for this vendor
- Access Controlsame class
- CWE-284other 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-94036 is D-Link DIR-X1860/DIR-X1860Z routerd ubus access control, a high vulnerability affecting DIR-X1860, DIR-X1860Z 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-94036. Public exploit evidence is: 1 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 8.8 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.
