VulnerabilityPublished 20 Feb 2026

CVE-2026-26048: Jinan USR IOT Technology Limited (PUSR) USR-W610 · Missing Authentication

Affects Jinan USR IOT Technology Limited (PUSR) USR-W610Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jinan USR IOT Technology Limited (PUSR)USR-W610	Affected <=3.1.1.0	Fixed in–

AI-suggested

Immediately assess whether the USR-W610 router firmware supports management frame protection (MFP) or 802.11w standards and enable this feature if available.
If MFP is not supported, consider deploying network segmentation to isolate critical wireless networks from less secure segments, limiting attack surface.
Implement wireless intrusion detection systems (WIDS) capable of detecting and alerting on deauthentication frame floods or anomalies.
Regularly monitor wireless network logs for unusual disassociation or deauthentication events that could indicate exploitation attempts.
Where possible, replace or upgrade affected routers with models that support robust management frame protection and have vendor patches available.
Educate network administrators about the risks of deauthentication attacks and ensure incident response plans include procedures for wireless DoS events.
Limit physical access to wireless infrastructure to reduce the risk of local attackers exploiting the vulnerability.
Coordinate with the vendor for firmware updates or patches addressing this vulnerability and apply them promptly once available.
Consider deploying additional authentication mechanisms such as WPA3, which inherently includes management frame protection, to enhance wireless security posture.

Description

The Wi-Fi router is vulnerable to de-authentication attacks due to the absence of management frame protection, allowing forged deauthentication and disassociation frames to be broadcast without authentication or encryption. An attacker can use this to cause unauthorized disruptions and create a denial-of-service condition.

Impact

The primary impact of CVE-2026-26048 is the ability for attackers to cause denial-of-service conditions by forcibly disconnecting clients from the Wi-Fi network through forged deauthentication frames. This can disrupt business operations, especially in environments relying heavily on wireless connectivity for critical services. The confidentiality impact is rated high because attackers can potentially intercept or manipulate network traffic during forced reconnections or exploit the disruption to facilitate further attacks. Although integrity and availability impacts are not directly affected, the disruption of service can lead to operational downtime and loss of productivity. Organizations using the USR-W610 router in enterprise, industrial, or critical infrastructure settings may face increased risk of targeted attacks aiming to disrupt communications. The ease of exploitation without requiring authentication or user interaction broadens the threat landscape, allowing remote attackers within wireless range to execute the attack. This vulnerability could also be exploited in coordinated attacks to cause widespread network outages or to distract security teams while other attacks are conducted. The lack of known exploits in the wild suggests the vulnerability is either newly discovered or underreported, but the potential for impact remains significant.

CWE-306Missing Authentication for Critical Functionality (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #21OWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Architecture and Design
Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
V1.2.4 (opens in a new tab)
Attack patterns
Choosing Message Identifier (opens in a new tab)
Force the System to Reset Values (opens in a new tab)
Using Unpublished Interfaces or Functionality (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
Communication Channel Manipulation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 14:22 UTC

WeaknessesCWE-306

Technical details

References

Community reviews

Related threats