Skip to content
Applications

CVE-2026-48161

9.3
Critical
EPSS 0.42%Patch availableAug 11, 2026

Unknown-source critical RCE (CVSS 9.3) with potential full system compromise.

common questions

Is CVE-2026-48161 being exploited?

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

How severe is CVE-2026-48161?

CVE-2026-48161 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-48161?

Yes. A fix has been recorded for CVE-2026-48161. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48161 affect?

CVE-2026-48161 affects Unknown - source blocked, Internet-facing services, Critical servers, Admin consoles. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48161?

Isolate exposed hosts, apply vendor patch when published, block exploit indicators, and increase logging/monitoring.

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

executive summary
technical analysis
affected
Unknown - source blockedInternet-facing servicesCritical serversAdmin consoles
impact

Unauthenticated remote code execution enabling full system takeover, data exfiltration, persistence, and lateral movement.

action required

Immediate action required

affected versions
dai-shi react18-use
  • affected>= 7b79148d1495a2505f9277da295a98cf176f4496 and <= 7b79148d1495a2505f9277da295a98cf176f4496

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