CVE-2025-71383

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 5 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Dbit WIFI4 N300 1.0.0 devices allow the management interface to be crashed via a request (from the local Wi-Fi network) that lacks a /api/login username or password field. This occurs because of an error in a JSON parser.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Anatomy of an IoT Exploit, From Hands-On to RCE: Folie a Deux!

https://www.klogixsecurity.com/scorpion-labs-blog/anatomy-of-an-iot-exploit-from-hands-on-to-rce-folie-a-deux

Vendor Advisories for CVE-2025-71383(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 45× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-12 23:14 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-12 16:45 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-12 04:18 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-11 23:53 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-11 19:29 UTCEG score recompute
  7. 2026-10-11 19:29 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-11 18:32 UTCEG score recompute
  9. 2026-10-11 15:07 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-11 15:06 UTCEG score recompute
  11. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-10-11 10:45 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 06:21 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-11 01:57 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 21:36 UTCEG score recompute
  16. 2026-10-10 21:36 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-10 17:14 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-10 12:54 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 08:32 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-10 04:10 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-09 23:48 UTCEG score recompute
  23. 2026-10-09 23:48 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-09 19:26 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 20 more
  1. 2026-10-09 15:06 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-09 10:18 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-09 05:50 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-09 01:29 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-08 21:08 UTCEG score recompute
  6. 2026-10-08 21:07 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-08 16:45 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-08 12:04 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-08 07:43 UTCEG score recompute
  11. 2026-10-08 07:43 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-08 03:21 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6
  13. 2026-10-08 02:56 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  14. 2026-10-08 02:56 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6
  15. 2026-10-08 02:56 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  16. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-06 20:17 UTCGHSA enrichmentGHSA-rmvf-vpmv-h9w6
  18. 2026-10-06 17:19 UTCNVD update
  19. 2026-10-06 17:02 UTCEG score recompute
  20. 2026-10-06 17:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71383?
CVE-2025-71383 is a critical-severity vulnerability; its CVE record was published on October 6, 2026. Dbit WIFI4 N300 1.0.0 devices allow the management interface to be crashed via a request (from the local Wi-Fi network) that lacks a /api/login username or password field. This occurs because of an error in a JSON parser.
When was the CVE record for CVE-2025-71383 published?
The CVE record for CVE-2025-71383 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2025-71383 actively exploited?
CVE-2025-71383 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71383?
CVE-2025-71383 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-71383?
No fix for CVE-2025-71383 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-71383 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-71383

Explore →

Is Your Infrastructure Affected by CVE-2025-71383?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs