CVE-2026-68502
Unauthenticated RCE in LazyOwn C2 via Socket.IO handler.
Is CVE-2026-68502 being exploited?
Not confirmed. CVE-2026-68502 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.70% probability of exploitation in the next 30 days.
How severe is CVE-2026-68502?
CVE-2026-68502 is rated Critical with a CVSS score of 9.8. 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-68502?
Yes. A fix has been recorded for CVE-2026-68502. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-68502 affect?
CVE-2026-68502 affects LazyOwn RedTeam/APT Framework < 0.2.154, lazyc2.py component, C2 servers running LazyOwn. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-68502?
Upgrade to 0.2.154 immediately; restrict/limit Socket.IO access and firewall C2 ports.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can run arbitrary shell commands in the C2 process, enabling code execution, server takeover, and post-compromise actions.
Immediate action required
- affected< 0.2.154
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.