Vulnerabilities in pkg:maven/org.geysermc.geyser/core
PACKAGECVE-2026-42188 is a LOW (CVSS 2.4) geyser vulnerable to server-side request vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Core libraries in the Maven ecosystem. The issue involves geyser vulnerable to server-side request forgery (ssrf) via player head texture url in geyser. Remediation is available by upgrading affected packages to version 2.9.3.
pkg:maven/org.geysermc.geyser/core
Vulnerability advisories affecting package pkg:maven/org.geysermc.geyser/core. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-xcfg-fcr5-gw9r | CVE-2026-42188 | LOW | Geyser Vulnerable to Server-Side Request Forgery (SSRF) via Player Head Texture URL in Geyser |
CVE-2026-42188 at a Glance
Security Impact
CVSS: 2.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-42188
To remediate this vulnerability, upgrade all affected Core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.geysermc.geyser</groupId>
<artifactId>core</artifactId>
<version>2.9.3</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.geysermc.geyser
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-42188, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.geysermc.geyser
Analyze the terminal output to locate any version of Core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.9.3), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.geysermc.geyser command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-42188 Affected Core Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.geysermc.geyser:core
|
Maven |
< 2.9.3
|
2.9.3
|
References
Frequently Asked Questions
What is CVE-2026-42188?
Which Core versions are affected?
What version fixes CVE-2026-42188?
Is core affected?
What is the CVSS score of CVE-2026-42188?
What CWE is associated with CVE-2026-42188?
How can I check Maven dependencies for CVE-2026-42188?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xcfg-fcr5-gw9r",
"modified" : "2026-05-13T14:19:57Z",
"published" : "2026-05-05T20:03:16Z",
"aliases" : [ "CVE-2026-42188" ],
"summary" : "Geyser Vulnerable to Server-Side Request Forgery (SSRF) via Player Head Texture URL in Geyser",
"details" : "### Summary\nA server-side request forgery (SSRF) vulnerability exists in Geyser’s handling of Bedrock player head texture data.\nBy supplying a crafted Base64-encoded skin texture URL via the /give command, an attacker can cause the Minecraft server to issue arbitrary HTTP GET requests to attacker-controlled or internal endpoints.\nThis occurs server-side, without proper URL validation, and can be triggered by a Bedrock client.\n\n### Details\nGeyser allows Bedrock clients to interact with Java Edition mechanics, including the creation of custom player heads using the minecraft:profile NBT structure.\n\nWhen a player head is created with a custom textures property, Geyser processes the Base64-encoded JSON value and forwards the embedded texture URL for resolution.\nHowever, the URL contained in the textures.SKIN.url field is not sufficiently validated.\n### PoC\n\n1. **Setup Environment:**\n - Set up a Minecraft Server (Paper/Spigot) with the latest version of Geyser installed.\n - Ensure you have a Bedrock client connected.\n\n2. **Prepare Listener:**\n - Go to [webhook.site](https://webhook.site) and obtain a unique URL (e.g., `https://webhook.site/YOUR-UUID`).\n\n3. **Construct Payload:**\n - Create a JSON payload pointing to your listener URL:\n `{\"textures\":{\"SKIN\":{\"url\":\"https://webhook.site/YOUR-UUID\"}}}`\n - Encode this JSON string to Base64.\n *(You can use a terminal command: `echo -n '{\"textures\":{\"SKIN\":{\"url\":\"...\"}}}' | base64`)*\n\n4. **Execute Command:**\n - Run the following command in the Bedrock Edition client:\n `/give @p minecraft:player_head[minecraft:profile={properties:[{name:\"textures\",value:\"[PASTE_BASE64_HERE]\"}]}]`\n\n5. **Verify:**\n - Check the webhook.site dashboard.\n - You will see an **HTTP GET request originating from the Minecraft Server's IP address**, not the client's IP.\n\n### Impact\nThis vulnerability allows server-side request forgery (SSRF) from the Minecraft server to arbitrary HTTP endpoints.\n\n#### Affected Parties\n- Minecraft servers running Geyser\n- Server operators exposing internal or cloud metadata endpoints\n\n#### Potential Impacts\n- Internal network probing (e.g., intranet services, admin panels)\n- Cloud metadata access attempts (e.g., 169.254.169.254)\n- IP address disclosure of the Minecraft server\n- Abuse of the server as an HTTP request proxy\n\nAlthough the vulnerability is blind SSRF (no response data returned to the attacker), it is still useful for:\n- Network mapping\n- Firewall bypass attempts\n- Cloud environment fingerprinting",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.geysermc.geyser:core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.9.3"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.9.2"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/GeyserMC/Geyser/security/advisories/GHSA-xcfg-fcr5-gw9r"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-42188"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/GeyserMC/Geyser"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-05T20:03:16Z",
"nvd_published_at" : "2026-05-11T22:22:11Z"
}
}