What is CVE-2026-24130?

CVE-2026-24130 is a low-severity security vulnerability in moonraker (pip), affecting versions < 0.10.0. It is fixed in 0.10.0.

Which versions of moonraker are affected by CVE-2026-24130?

moonraker (pip) versions < 0.10.0 is affected.

Is there a fix for CVE-2026-24130?

Yes. CVE-2026-24130 is fixed in 0.10.0. Upgrade to this version or later.

Is CVE-2026-24130 exploitable, and should I be worried?

Whether CVE-2026-24130 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-24130 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-24130?

Upgrade moonraker to 0.10.0 or later.

CVE-2026-24130 in moonraker

Q: Which versions of moonraker are affected by CVE-2026-24130?

moonraker (pip) versions < 0.10.0 is affected.

Q: Is there a fix for CVE-2026-24130?

Yes. CVE-2026-24130 is fixed in 0.10.0. Upgrade to this version or later.

Q: Is CVE-2026-24130 exploitable, and should I be worried?

Whether CVE-2026-24130 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-24130 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-24130?

Upgrade moonraker to 0.10.0 or later.

Summary

Moonraker affected by LDAP search filter injection

Workarounds

Admins can set the max_login_attempts option in the [authorization] section to a reasonable value. Any IP attempting to exploit this vulnerability will be locked out after it has reached the specified number of consecutive failed login attempts. This condition is cleared after a Moonraker restart. Note that if an attacker knows a valid user password they can bypass this protection by successfully logging in.

The most secure workaround for users unable to upgrade is to remove the ldap section from moonraker.conf and rely on the built in user authentication.

Impact

Instances of Moonraker configured with the ldap component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes.

Affected versions

moonraker (< 0.10.0)

Security releases

moonraker → 0.10.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Users should upgrade to Moonraker 0.10.0 which patches this vulnerability.

Frequently Asked Questions

What is CVE-2026-24130? CVE-2026-24130 is a low-severity security vulnerability in moonraker (pip), affecting versions < 0.10.0. It is fixed in 0.10.0.
Which versions of moonraker are affected by CVE-2026-24130? moonraker (pip) versions < 0.10.0 is affected.
Is there a fix for CVE-2026-24130? Yes. CVE-2026-24130 is fixed in 0.10.0. Upgrade to this version or later.
Is CVE-2026-24130 exploitable, and should I be worried? Whether CVE-2026-24130 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-24130 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-24130? Upgrade moonraker to 0.10.0 or later.