# CVE-2026-92704: SharpEmu: Cross-site request forgery in the debugger frontend leads to arbitrary process execution

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

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

## Remediation

No remediation reported in collected sources

## Affected products and versions

- sharpemu / sharpemu: < 0.0.3-release.3-patch.1 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 8.3 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H; source: CNA: GitHub_M

- CVSS 3.1: 8.3 (high); CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H; source: NVD: security-advisories@github.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-306, CWE-346, CWE-350, CWE-352, CWE-749

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3 (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/sharpemu/sharpemu/pull/858 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463 (security-advisories@github.com)

- https://github.com/sharpemu/sharpemu/pull/858 (security-advisories@github.com)

- https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1 (security-advisories@github.com)

- https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3 (security-advisories@github.com)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-92704; retrieved 2026-11-04; source updated 2026-11-04

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92704; retrieved 2026-11-04; source updated 2026-11-04

Revision: 966612557ce1f8e4bfa239ef331ca5bbbc7ba0fcf36a2d84b6692ba3261a7db0

Canonical: https://y2.dev/cve/CVE-2026-92704

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.