What is CVE-2026-40177?

CVE-2026-40177 is a critical-severity improper authentication vulnerability in ajenti.plugin.core (pip), affecting versions < 0.112. It is fixed in 0.112. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2026-40177?

CVE-2026-40177 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ajenti.plugin.core are affected by CVE-2026-40177?

ajenti.plugin.core (pip) versions < 0.112 is affected.

Is there a fix for CVE-2026-40177?

Yes. CVE-2026-40177 is fixed in 0.112. Upgrade to this version or later.

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

Whether CVE-2026-40177 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-40177 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-40177?

Upgrade ajenti.plugin.core to 0.112 or later.

CVE-2026-40177 in ajenti.plugin.core | Intelligent Application Security

Q: How severe is CVE-2026-40177?

CVE-2026-40177 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ajenti.plugin.core are affected by CVE-2026-40177?

ajenti.plugin.core (pip) versions < 0.112 is affected.

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

Yes. CVE-2026-40177 is fixed in 0.112. Upgrade to this version or later.

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

Whether CVE-2026-40177 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-40177 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-40177?

Upgrade ajenti.plugin.core to 0.112 or later.

Summary

ajenti.plugin.core has password bypass when 2FA is activated

Impact

If the 2FA was activated, it was possible to bypass the password authentication

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-40177 has a CVSS score of 7.5 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.112); upgrading removes the vulnerable code path.

Affected versions

ajenti.plugin.core (< 0.112)

Security releases

ajenti.plugin.core → 0.112 (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.

See it in your environment

Remediation advice

This is fixed in the version 0.112. Users should upgrade to this version as soon as possible.

Frequently Asked Questions

What is CVE-2026-40177? CVE-2026-40177 is a critical-severity improper authentication vulnerability in ajenti.plugin.core (pip), affecting versions < 0.112. It is fixed in 0.112. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2026-40177? CVE-2026-40177 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ajenti.plugin.core are affected by CVE-2026-40177? ajenti.plugin.core (pip) versions < 0.112 is affected.
Is there a fix for CVE-2026-40177? Yes. CVE-2026-40177 is fixed in 0.112. Upgrade to this version or later.
Is CVE-2026-40177 exploitable, and should I be worried? Whether CVE-2026-40177 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-40177 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-40177? Upgrade ajenti.plugin.core to 0.112 or later.

Other vulnerabilities in ajenti.plugin.core

CVE-2026-40177