CVE-2026-45289
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloudburstMC Protocol is a protocol library for Minecraft Bedrock Edition. Prior to version 3.0.0.Beta12-20260420.182526-15, CloudburstMC Protocol is partially missing validation for FULL type authentication tokens (Cloudburst/Protocol). This vulnerability impacts publicly accessible software depending on the affected versions of Protocol, specifically the EncryptionUtils methods to validate auth payloads for FULL type tokens. This issue has been patched in version 3.0.0.Beta12-20260420.182526-15.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCloudburstMC Protocol library for Minecraft Bedrock Edition is missing validation for FULL type authentication tokens in EncryptionUtils methods. This allows auth payload bypass in publicly accessible software depending on affected versions, potentially enabling unauthorized access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate CloudburstMC Protocol library in your environmentSearch your project dependencies (Maven pom.xml, Gradle build.gradle, or look for cloudburst-protocol in your lib/ directory) for the CloudburstMC Protocol library. Check your dependency management system or compiled JAR files for 'cloudburst' or 'protocol' related artifacts.Affected if The library is present in your dependencies or deployed artifacts
-
Determine the installed versionRead the version number from your dependency file (pom.xml, build.gradle) or JAR manifest. If using a packaged application, check the filename or metadata for a version string containing 'Beta' or date stamps.Affected if Version is present and is any build earlier than 3.0.0.Beta12-20260420.182526-15
-
Verify the EncryptionUtils authentication module is in useInspect your codebase or running service for imports or references to 'EncryptionUtils' class from the CloudburstMC Protocol library. Check if your authentication flow calls methods that handle FULL type authentication tokens.Affected if Your application uses EncryptionUtils methods for processing FULL type authentication tokens
-
Check if the affected service is network-accessibleDetermine whether any service using the CloudburstMC Protocol library is exposed to network connections from untrusted sources. Review firewall rules, exposed ports, or public endpoint configurations.Affected if The service using this library is reachable from public or untrusted networks
-
Review authentication token handling logicExamine your authentication implementation code to see how FULL type tokens are processed through EncryptionUtils. Look for token validation routines and verify whether explicit validation for FULL type tokens exists.Affected if FULL type tokens are processed without explicit validation checks in your code
Your environment is affected if CloudburstMC Protocol library version earlier than 3.0.0.Beta12-20260420.182526-15 is deployed and your service uses EncryptionUtils to handle FULL type authentication tokens, especially if exposed to untrusted network access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade CloudburstMC Protocol to version 3.0.0.Beta12-20260420.182526-15 or later which includes the missing validation fix.
3.0.0.Beta12-20260420.182526-15
- 1. Identify all projects and dependencies that use CloudburstMC Protocol library
- 2. Locate the dependency management file (e.g., pom.xml, build.gradle, or package.json) where CloudburstMC Protocol is declared
- 3. Update the CloudburstMC Protocol dependency version to 3.0.0.Beta12-20260420.182526-15 or later
- 4. Verify the dependency update was successful by checking the resolved library version
- 5. Rebuild the project to ensure compilation succeeds with the new version
- 6. Test the application to confirm authentication functionality works correctly with the patched library
- 7. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45289 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45289 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data