Skip to content
IoT

CVE-2026-9543

8.9
High
EPSS 2%May 26, 2026

Remote OS command injection in Totolink N300RH Web UI via admpass.

common questions

Is CVE-2026-9543 being exploited?

Not confirmed. CVE-2026-9543 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 2.1% probability of exploitation in the next 30 days.

How severe is CVE-2026-9543?

CVE-2026-9543 is rated High with a CVSS score of 8.9. 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-9543?

Not known from our data. No patch reference has been recorded for CVE-2026-9543, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-9543 affect?

CVE-2026-9543 affects Totolink N300RH firmware 6.1c.1353_B20190305 (Web UI). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-9543?

Apply firmware update when available; disable remote admin; restrict WAN access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Totolink N300RH firmware 6.1c.1353_B20190305 (Web UI)
impact

Remote attacker can execute commands on the device via the web management interface, potentially full device compromise and network access.

action required

Immediate action required

affected versions
Totolink N300RH
  • affected6.1c.1353_B20190305

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free