CVE-2026-40177
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 · uneditedajenti.plugin.core defines all necessary core elements to allow Ajenti to run properly. Prior to 0.112, if the 2FA was activated, it was possible to bypass the password authentication This vulnerability is fixed in 0.112.
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 confidenceThe ajenti.plugin.core plugin versions prior to 0.112 contain an authentication bypass vulnerability where password authentication can be circumvented even when 2FA is activated, allowing unauthorized access to the Ajenti administration panel.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.112CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify ajenti.plugin.core versionRun 'pip show ajenti.plugin.core' or check the installed package version via your package managerAffected if The displayed version is lower than 0.112 (e.g., 0.111, 0.110, etc.)
-
Locate the Ajenti configuration fileCheck common locations such as /etc/ajenti/config.json or ~/.ajenti/config.json for the Ajenti panel configurationAffected if The configuration file exists and contains Ajenti settings
-
Verify if 2FA is enabledInspect the configuration file for 'two_factor_auth', '2fa', or similar 2FA-related settings and check if they are set to true or enabledAffected if 2FA is explicitly enabled in the Ajenti configuration
-
Confirm vulnerability applicabilityCross-reference: if the installed ajenti.plugin.core version is below 0.112 AND 2FA is enabled in the configuration, the environment is vulnerable to the authentication bypassAffected if Both conditions are true: version < 0.112 AND 2FA is enabled
Your environment is affected if ajenti.plugin.core version is below 0.112 and two-factor authentication is enabled in your Ajenti configuration.
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 · scoped0.112
Upgrade ajenti.plugin.core to version 0.112 or later to resolve the 2FA bypass vulnerability.
0.112
- Check the current version of ajenti.plugin.core installed (e.g., pip show ajenti.plugin.core or via package manager)
- Upgrade ajenti.plugin.core to version 0.112 or later (e.g., pip install --upgrade ajenti.plugin.core or use your system's package manager)
- Restart the Ajenti service to apply the update
- Verify the installed version is 0.112 or higher
- Test that 2FA authentication is working correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40177 — 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-40177 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