{"answers":{"affected":"2 open source packages ship an affected version, including org.geysermc.geyser:core. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42188 exists.","fix":"Upgrade org.geysermc.geyser:core to 2.9.3 or later.","what":"CVE-2026-42188 is a low-severity server-side request forgery vulnerability in GeyserMC Geyser, published on 11 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42188 and fix it if it is affected.\n\nWhat it is: CVE-2026-42188 is a low-severity server-side request forgery vulnerability in GeyserMC Geyser, published on 11 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42188 exists.\n\nAffected packages and fixed versions:\n- org.geysermc.geyser:core (Maven): affected all versions; fixed in 2.9.3\n- org.geysermc.geyser:core (Maven): affected all versions; fixed in 2.9.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42188/ (Markdown: https://insights.sbomify.com/CVE-2026-42188/index.md)","id":"CVE-2026-42188","markdown":"https://insights.sbomify.com/CVE-2026-42188/index.md","name":"CVE-2026-42188","record":{"aliases":["GHSA-xcfg-fcr5-gw9r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Minecraft bridge server","requires_auth":"high_privilege","summary":"Attackers can force the Minecraft server to make arbitrary HTTP requests via crafted player head texture URLs, potentially accessing internal services.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"geyser","vendor":"geysermc"}],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Geyser is a bridge between Minecraft: Bedrock Edition and Minecraft: Java Edition. Prior to 2.9.3, a server-side request forgery (SSRF) vulnerability exists in Geyser’s handling of Bedrock player head texture data. By 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. This occurs server-side, without proper URL validation, and can be triggered by a Bedrock client. This vulnerability is fixed in 2.9.3.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Geyser: Server-Side Request Forgery (SSRF) via Player Head Texture URL","id":"CVE-2026-42188","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Russh: Pre-auth DoS via unbounded allocation in keyboard-interactive auth","id":"CVE-2026-42189"},"packages":[{"ecosystem":"Maven","fixed":["2.9.3"],"introduced":["0"],"last_affected":[],"package":"org.geysermc.geyser:core","purl":null,"source":"GHSA-xcfg-fcr5-gw9r"},{"ecosystem":"Maven","fixed":["2.9.3"],"introduced":["0"],"last_affected":[],"package":"org.geysermc.geyser:core","purl":"pkg:maven/org.geysermc.geyser/core","source":"GHSA-xcfg-fcr5-gw9r"}],"prev":{"headline":"OpenBao's Namespace Deletion May Not Delete Data Properly","id":"CVE-2026-42186"},"products":["Geyser"],"published":"2026-05-11","related":[{"cvss_score":7.4,"headline":"User impersonation due to incorrect handling of the login JWT","id":"CVE-2021-39177","kev_date_added":null,"published":"2021-08-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["GeyserMC"]},"summary":"Attackers can force the Minecraft server to make arbitrary HTTP requests via crafted player head texture URLs, potentially accessing internal services.","url":"https://insights.sbomify.com/CVE-2026-42188/"}