CVE-2026-11374
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 · uneditedIn ManageEngine ADSelfService Plus, RecoveryManager Plus, M365 Manager Plus, and ADAudit Plus, the SSO tickets generated to authenticate that session could be predicted by an unauthenticated user, leading to account takeover.
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 confidenceThis vulnerability in ManageEngine ADSelfService Plus, RecoveryManager Plus, M365 Manager Plus, and ADAudit Plus allows unauthenticated attackers to predict SSO tickets used for session authentication due to insufficient randomness in ticket generation. Attackers can forge valid session tokens and achieve account takeover without any credentials.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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 installed ManageEngine productsReview installed software or running services on the system for any of the following: ADSelfService Plus, RecoveryManager Plus, M365 Manager Plus, ADAudit Plus. Check Windows Services, Linux service listings, or application directories.Affected if Any of these four ManageEngine products are present on the system
-
Determine the installed product versionLocate the version information in the product's admin console, about page, or check the installation directory for a version file. Common locations include the product's bin folder or a version.txt file within the installation root.Affected if The installed version matches or precedes the versions listed in the vendor security advisory (compare against official CVE documentation)
-
Confirm SSO authentication is enabledLog into the product admin console and navigate to the authentication or security settings. Check whether Single Sign-On (SSO) or session-based authentication using SSO tickets is configured and active.Affected if SSO authentication is enabled and in use for user sessions
-
Review authentication logs for anomalous patternsExamine the product's audit or security logs for any suspicious authentication activity, particularly multiple failed login attempts followed by successful token-based sessions, or unusual ticket reuse patterns.Affected if Logs show unexpected session tokens or authentication anomalies that suggest ticket prediction may have occurred
A user is affected if they run any of the four ManageEngine products with SSO enabled and their version matches the vulnerable range per official vendor documentation.
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.
From vendor dataUpgrade to vendor-provided patches addressing this issue. If no patch is immediately available, consider restricting access to the affected endpoints via network controls while the vendor fix is being applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11374 — 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-11374 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