CVE-2026-35075
Unauthenticated attacker retrieves default firmware password to gain full device access.
Is CVE-2026-35075 being exploited?
Not confirmed. CVE-2026-35075 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-35075?
CVE-2026-35075 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-35075?
Yes. A fix has been recorded for CVE-2026-35075. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35075 affect?
CVE-2026-35075 affects Unspecified devices with vulnerable firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35075?
Apply vendor firmware update when released; disable default credentials if possible.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote, unauthenticated access via default password enables full device takeover.
Patch when available
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
- affected>= V1_00_00 and < V6_00_07
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.