CVE-2026-92704 (GCVE-0-2026-92704)
Vulnerability from cvelistv5 – Published: 2026-11-04 15:24 – Updated: 2026-11-04 15:24
VLAI
EPSS
VEX
Title
SharpEmu: Cross-site request forgery in the debugger frontend leads to arbitrary process execution
Summary
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
Severity
8.3 (High)
CWE
Assigner
References
4 references
| URL | Tags |
|---|---|
| https://github.com/sharpemu/sharpemu/security/adv… | x_refsource_CONFIRM |
| https://github.com/sharpemu/sharpemu/pull/858 | x_refsource_MISC |
| https://github.com/sharpemu/sharpemu/commit/3831f… | x_refsource_MISC |
| https://github.com/sharpemu/sharpemu/releases/tag… | x_refsource_MISC |
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"product": "sharpemu",
"vendor": "sharpemu",
"versions": [
{
"status": "affected",
"version": "\u003c 0.0.3-release.3-patch.1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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 \u00a0do_POST\u00a0 handler in \u00a0tools/SharpEmu.DebuggerFrontend/debugger_frontend.py\u00a0 does not validate the Origin, Referer, Sec-Fetch-Site, or Host headers. The \u00a0_read_json_body()\u00a0 function also accepts JSON sent with browser-simple content types instead of requiring \u00a0application/json\u00a0. A malicious page that can reach the loopback listener can send cross-origin requests to \u00a0/api/launch\u00a0, \u00a0/api/command\u00a0, and \u00a0/api/connect\u00a0. 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 \u00a0/api/launch\u00a0 endpoint accepts an attacker-selected \u00a0emulatorPath\u00a0 if it points to an existing file on the victim\u2019s host. On POSIX systems, that file must also be executable. The endpoint additionally requires an existing \u00a0ebootPath\u00a0. The \u00a0/api/command\u00a0 endpoint exposes debugger operations, including \u00a0write-memory\u00a0, \u00a0set-register\u00a0, and \u00a0continue\u00a0. The \u00a0/api/connect\u00a0 endpoint can initiate outbound TCP connections. These operations can let an attacker execute an existing binary with the victim\u2019s 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"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-306",
"description": "CWE-306: Missing Authentication for Critical Function",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-346",
"description": "CWE-346: Origin Validation Error",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-350",
"description": "CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-352",
"description": "CWE-352: Cross-Site Request Forgery (CSRF)",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-749",
"description": "CWE-749: Exposed Dangerous Method or Function",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-04T15:24:16.625Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3"
},
{
"name": "https://github.com/sharpemu/sharpemu/pull/858",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/sharpemu/sharpemu/pull/858"
},
{
"name": "https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463"
},
{
"name": "https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1"
}
],
"source": {
"advisory": "GHSA-fr3v-rvqp-8fx3",
"discovery": "UNKNOWN"
},
"title": "SharpEmu: Cross-site request forgery in the debugger frontend leads to arbitrary process execution"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-92704",
"datePublished": "2026-11-04T15:24:16.625Z",
"dateReserved": "2026-09-16T16:22:31.542Z",
"dateUpdated": "2026-11-04T15:24:16.625Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-92704",
"date": "2026-11-08",
"epss": "0.00158",
"percentile": "0.05018"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "sharpemu",
"vendor": "sharpemu",
"versions": [
{
"status": "affected",
"version": "\u003c 0.0.3-release.3-patch.1"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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 \u00a0do_POST\u00a0 handler in \u00a0tools/SharpEmu.DebuggerFrontend/debugger_frontend.py\u00a0 does not validate the Origin, Referer, Sec-Fetch-Site, or Host headers. The \u00a0_read_json_body()\u00a0 function also accepts JSON sent with browser-simple content types instead of requiring \u00a0application/json\u00a0. A malicious page that can reach the loopback listener can send cross-origin requests to \u00a0/api/launch\u00a0, \u00a0/api/command\u00a0, and \u00a0/api/connect\u00a0. 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 \u00a0/api/launch\u00a0 endpoint accepts an attacker-selected \u00a0emulatorPath\u00a0 if it points to an existing file on the victim\u2019s host. On POSIX systems, that file must also be executable. The endpoint additionally requires an existing \u00a0ebootPath\u00a0. The \u00a0/api/command\u00a0 endpoint exposes debugger operations, including \u00a0write-memory\u00a0, \u00a0set-register\u00a0, and \u00a0continue\u00a0. The \u00a0/api/connect\u00a0 endpoint can initiate outbound TCP connections. These operations can let an attacker execute an existing binary with the victim\u2019s 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"
}
],
"id": "CVE-2026-92704",
"lastModified": "2026-11-04T16:17:55.097",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.6,
"impactScore": 6.0,
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2026-11-04T16:17:55.097",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/sharpemu/sharpemu/commit/3831f3c407c547a5e58f353649b2c556d785c463"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/sharpemu/sharpemu/pull/858"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/sharpemu/sharpemu/releases/tag/v0.0.3-release.3-patch.1"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/sharpemu/sharpemu/security/advisories/GHSA-fr3v-rvqp-8fx3"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-306"
},
{
"lang": "en",
"value": "CWE-346"
},
{
"lang": "en",
"value": "CWE-350"
},
{
"lang": "en",
"value": "CWE-352"
},
{
"lang": "en",
"value": "CWE-749"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.