---
id: "CVE-2026-92704"
kind: "vulnerability"
aliases: ["CVE-2026-92704"]
title: "SharpEmu: debugger frontend lets malicious web pages launch programs"
severity: "high"
cvss: 8.3
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["debugger-frontend", "linux", "other", "ps5-emulator", "sharpemu", "windows"]
not_affected_if: ["debugger-frontend-not-running", "release-archives-only"]
published_at: "2026-11-04T16:17:55+00:00"
first_seen_at: "2026-11-04T16:28:15+00:00"
updated_at: "2026-11-04T16:28:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-92704", "first_seen_at": "2026-11-04T16:28:15+00:00"}]
---

# SharpEmu: debugger frontend lets malicious web pages launch programs

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the SharpEmu version: `0.0.3-release.3` and earlier are affected.
- Check whether `tools/SharpEmu.DebuggerFrontend/debugger_frontend.py` exists and is running on 127.0.0.1:8765.
- The sources say the tooling is not included in release archives, so check whether the repository source was run.

## Fix

- SharpEmu: `0.0.3-release.3-patch.1`

## Timeline

- 2026-11-04T16:28:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-92704

## Documents

- [advisory] Vendor advisory: github.com https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3
- [fix] Patch: github.com https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463
- [fix] Release notes: github.com https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1

## From the sources

SharpEmu 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

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_