dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-24871

CRITICAL · 10.0 CVSS v4.0 Published 2026-01-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in pilgrimage233 Minecraft-Rcon-Manage.This issue affects Minecraft-Rcon-Manage: before 3.0.

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 · high confidence

A code injection vulnerability exists in Minecraft-Rcon-Manage versions before 3.0, allowing attackers to inject and execute arbitrary code through improper handling of user input or RCON command parameters. This remote code execution vulnerability carries a CVSS 10 rating due to the critical nature of code injection flaws.

MitigationUpgrade to Minecraft-Rcon-Manage version 3.0 or later to obtain the patched version. If immediate upgrading is not feasible, implement strict input validation and sanitization on all RCON command inputs, and restrict network access to the RCON interface.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Minecraft-Rcon-Manage is installed
    Check for the presence of Minecraft-Rcon-Manage in your system, such as looking for its process, installation directory, or checking installed packages. Common locations include /opt/, /usr/local/, or within the Minecraft server plugins folder.
    Affected if Minecraft-Rcon-Manage is found on the system
  2. Determine the installed version
    Locate and read the version information file, or run the command 'minecraft-rcon-manage --version' or check the package manager if installed via apt/yum. Compare the version number against 3.0.
    Affected if The installed version is any version before 3.0 (e.g., 2.x, 1.x)
  3. Verify the RCON interface is enabled
    Inspect the configuration file (commonly config.json, config.yml, or rcon.conf in the application directory) and check for an 'enabled' or 'rcon' setting set to true, or verify the application is listening on the default RCON port (typically 25575).
    Affected if RCON functionality is enabled and the service is running
  4. Check network exposure of RCON service
    Review network configuration, firewall rules, or the application's bind address setting to determine if the RCON interface is accessible from network locations rather than localhost only.
    Affected if The RCON interface is bound to a non-localhost address or is accessible remotely

You are affected if Minecraft-Rcon-Manage version is before 3.0 AND the RCON interface is enabled and accessible, allowing unauthenticated or attacker-controlled input to reach the command processing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Minecraft-Rcon-Manage version 3.0 or later to obtain the patched version. If immediate upgrading is not feasible, implement strict input validation and sanitization on all RCON command inputs, and restrict network access to the RCON interface.

Recommended fix Moderate confidence

version 3.0 or later

  1. 1. Backup your current Minecraft-Rcon-Manage configuration and any important data
  2. 2. Navigate to the GitHub repository (pilgrimage233/Minecraft-Rcon-Manage)
  3. 3. Download version 3.0 or the latest stable release
  4. 4. Replace the existing installation files with the new version
  5. 5. Restore your configuration from the backup
  6. 6. Start the application and verify it runs without errors
  7. 7. Test RCON functionality to ensure the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24871 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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