# CVE-2026-68502: LazyOwn: Unauthenticated Socket.IO `input` Event Reaches LazyOwn Command Dispatcher — Unauthenticated RCE

> Unauthenticated attackers can execute arbitrary commands on the LazyOwn C2 server via the Socket.IO input event handler.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-fr84-8cfg-59w4

## What is CVE-2026-68502?

CVE-2026-68502 is a critical command injection vulnerability in grisuno LazyOwn, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LazyOwn RedTeam/APT Framework is an AI-powered C2 and red-team operations framework. Prior to 0.2.154, LazyOwn's lazyc2.py registers an unauthenticated Socket.IO input event handler that dispatches data.get('value') to LazyOwnShell.one_cmd, reaching LazyOwnShell.do_cmd and subprocess.call(command, shell=True), allowing unauthenticated remote code execution in the C2 process. This issue is fixed in 0.2.154.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-68502?


## How do I fix CVE-2026-68502?

No fix has been published for CVE-2026-68502 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-68502 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68502 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68502 and fix it if it is affected.

What it is: CVE-2026-68502 is a critical command injection vulnerability in grisuno LazyOwn, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68502 exists.

Affected product: grisuno LazyOwn. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68502/ (Markdown: https://insights.sbomify.com/CVE-2026-68502/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68502
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68502
- OSV: https://osv.dev/vulnerability/CVE-2026-68502

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68502/
Summaries are generated and may contain mistakes; the official description above is the record.