CVE-2026-92704 · Other
NO FIX YET · SEE WHAT TO DO
SharpEmu's repository debugger frontend runs an unauthenticated HTTP API on 127.0.0.1:8765 that accepts cross-origin requests from web pages. A malicious page can make the victim's browser launch an existing executable, write emulated process memory, change registers, or open outbound TCP connections.
first public Sep 16, 2026 · 1 source
Is this in your stack? Find out in 2 minutes.
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Only people who run the repository's debugger frontend tooling alongside SharpEmu are exposed. The sources say this tooling is not in the release archives, so people using only the release builds are not affected. Chromium may block some of these requests unless Local Network Access is granted, but the sources say this restriction is not applied consistently.
Not affected if debugger-frontend-not-running, release-archives-only
Who cares debugger-frontend, linux, ps5-emulator, sharpemu, windows
0.0.3-release.3 and earlier are affected.tools/SharpEmu.DebuggerFrontend/debugger_frontend.py exists and is running on 127.0.0.1:8765.0.0.3-release.3-patch.1SharpEmu is an experimental PlayStation 5 emulator for Windows and Linux. In version 0.0.3-release.3 and earlier, the repository-provided debugger frontend tooling is vulnerable while running. This tooling is not included in the release archives. The frontend exposes an HTTP API on 127.0.0.1:8765 without authentication or CSRF token. Its do_POST handler in tools/SharpEmu.DebuggerFrontend/debugger_frontend.py does not validate the Origin, Referer, Sec-Fetch-Site, or Host headers. The _read_json_body() function also accepts JSON sent with browser-simple content types instead of requiring application/json . A malicious page that can reach the loopback listener can send cross-origin requests to /api/launch , /api/command , and /api/connect . Chromium may require Local Network Access permission for pages served from public origins. Local-origin pages and other delivery paths are not consistently subject to this restriction. The /api/launch endpoint accepts an attacker-selected emulatorPath if it points to an existing file on the victim’s host. On POSIX systems, that file must also be executable. The endpoint additionally requires an existing ebootPath . The /api/command endpoint exposes debugger operations, including write-memory , set-register , and continue . The /api/connect endpoint can initiate outbound TCP connections. These operations can let an attacker execute an existing binary with the victim’s privileges, control the attached emulated process, or reach network services accessible from the host. DNS rebinding can additionally let the attacker read API responses interactively. This issue is fixed in version 0.0.3-release.3-patch.1
This page as .md · .json · in your agent: get_signal("CVE-2026-92704") · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.