Skip to content

DoS in Geyser's Bedrock packet handling

Moderate
onebeastchris published GHSA-m2q6-2hwr-643w Jul 31, 2025

Package

No package listed

Affected versions

< Geyser build 897

Patched versions

Geyser build 897

Description

Impact

This vulnerability impacts publicly accessible Geyser instances on the affected versions by allowing an attacker to overload Geyser instances under specific circumstances.

Patches

Geyser builds 897 and up have been patched. We urge users to update as soon as possible.

Downloads are available on the official download website: https://geysermc.org/download/

Notes

The fix further introduces a per-address connection limit. By default, it's set to a maximum of 10 connections per address, but can be increased using the -DGeyser.MaxConnectionsPerAddress system property to e.g. account for CGNAT use where more connections per-ip could happen.

Workarounds

There are no known workarounds besides updating Geyser to the latest version.

Response to this vulnerability was supported by the Open Collaboration Project. We would like to thank all maintainers and volunteers who helped support the response.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits