CVE-2026-92704

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

Products / packages sharpemu

Published 04/11/2026, 15:24:16 UTC

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:05:30 UTC

GitHub_M · CVSS:3.1 · 8.3

Assessment vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Severity

high8.3

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Exploit reference published

Source-linked evidence; not proof of attacks in the wild or independent validation.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

SharpEmu versions before 0.0.3-release.3-patch.1 are vulnerable to cross-site request forgery, allowing an attacker with access to the loopback listener to execute arbitrary processes. The debugger frontend exposes an HTTP API without authentication. An attacker can send cross-origin requests to certain endpoints.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

Chromium may require Local Network Access permission for pages served from public origins. The endpoint additionally requires an existing ebootPath .

Excerpt from the original source description below.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

sharpemu · GitHub_M

sharpemu

1 range

GitHub_M version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

< 0.0.3-release.3-patch.1

Other versions: unknown

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.

sharpemu/sharpemu · security/advisories/GHSA-fr3v-rvqp-8fx3 ↗Attributed to CISA-ADP

Original source description

Read the full publisher description

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

References

4 sources

sharpemu/sharpemu · security/advisories/GHSA-fr3v-rvqp-8fx3

Public exploit referenceGitHub_M · CISA-ADP

sharpemu/sharpemu · pull request #858

PatchGitHub_M

sharpemu/sharpemu · commit 3831f3c

PatchGitHub_M

sharpemu/sharpemu · releases/tag/v0.0.3-release.3-patch.1

Release notesGitHub_M

Inside the record

Evidence available

Package identity · not supplied

Version evidence

Remediation guidance · not supplied

Weakness classification

Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-92704

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-306 ↗

CWE-306: Missing Authentication for Critical Function

GitHub_M

CWE-346 ↗

CWE-346: Origin Validation Error

GitHub_M

CWE-350 ↗

CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action

GitHub_M

CWE-352 ↗

CWE-352: Cross-Site Request Forgery (CSRF)

GitHub_M

CWE-749 ↗

CWE-749: Exposed Dangerous Method or Function

GitHub_M

Contributing organizations · 2

GitHub_M

Assigning organization

2026-11-04

CISA-ADP

Additional data publisher

2026-11-09

Timeline

All times UTC

4 Nov 2026, 15:24
Advisory published
Publication date supplied by the source.
9 Nov 2026, 16:33
Source updated
Latest modification date supplied by the source.
9 Nov 2026, 16:41
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

CVE · CVE-2026-927042026-11-09

Observed 2026-11-09T16:41:02.276Z · upstream updated 2026-11-09T16:33:41.642Z

Prioritization updated

before

[]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-09T16:31:05.128810Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "poc"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "total"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. The headline is the highest imported catalog score; sources may disagree.
Observed exploitation · KEV: An absent or unavailable KEV listing does not establish that exploitation has not occurred.
Predicted exploitation · EPSS: No EPSS estimate available in this record.

CISA-ADP · SSVC

CISA Coordinator · 2026-11-09

Exploitation: poc
Automatable: no
Technical Impact: total

SSVC describes the publisher’s decision context. Your organization’s exposure and priorities may differ.

Record identifiers

Aliases: None recorded

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

CVE CVE-2026-92704

Enrichment coverage

NVDAvailable

Checked 04/11/2026, 16:45:36 UTC

GHSANo result

Checked 04/11/2026, 16:45:37 UTC

EUVDAvailable

Checked 04/11/2026, 16:45:37 UTC

EPSSNo result

Checked 04/11/2026, 16:45:37 UTC

Additional source evidence

NVD · CVE-2026-92704

CVSS 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Checked 04/11/2026, 16:45:36 UTC

ENISA EUVD · EUVD-2026-116942

CVSS 8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Checked 04/11/2026, 16:45:37 UTC

Sponsored by MoxsoBuild security habits with adaptive training and phishing simulations.View as JSON

Investigate in your agent.

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

Severity and exploitation

What this means

Attack conditions

Affected versions

sharpemu

affected

unaffected

unknown

What to do

Public exploit evidence

Original source description

References

Inside the record

Evidence available

Original records

Underlying weaknesses

Timeline

Advisory published

Source updated

Last imported by cve.new

What changed