Unauthenticated RCE via Socket.IO input handler
Published Jul 30, 2026 · Updated Jul 30, 2026
Missing authentication in LazyOwn before 0.2.154 allows remote attackers to execute arbitrary commands through a Socket.IO event. The input handler passes data.get('value') to LazyOwnShell.one_cmd and ultimately subprocess.call with shell=True without checking the Socket.IO session. Network access to the C2 service is sufficient, and commands run with the C2 process's operating-system privileges.
Summary
What happened
Missing authentication in LazyOwn before 0.2.154 allows remote attackers to execute arbitrary commands through a Socket.IO event. The input handler passes data.get('value') to LazyOwnShell.one_cmd and ultimately subprocess.call with shell=True without checking the Socket.IO session. Network access to the C2 service is sufficient, and commands run with the C2 process's operating-system privileges.
The record
- CVE
- CVE-2026-68502
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- grisuno
- Product
- LazyOwn
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.2.154
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo