CVE-2026-58222
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 · uneditedA security flaw combining LDAP filter injection and improper authorization checks was found in Samba Active Directory Domain Controller (AD DC). When processing LDAP Compare requests, Samba fails to properly validate user-supplied attribute names and executes the resulting internal database search in a trusted context, bypassing normal Access Control List (ACL) enforcement. An authenticated low-privilege domain user can exploit these flaws to disclose confidential Active Directory attributes that would normally be inaccessible. The disclosed information may be leveraged to derive sensitive authentication material, potentially leading to privilege escalation and complete domain compromise. For example: In deployments configured with Group Managed Service Accounts (gMSAs), an attacker can extract the "msKds-RootKeyData" attribute and derive gMSA passwords offline, potentially leading to complete domain compromise if privileged gMSAs are present.
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 confidenceSamba AD DC fails to validate user-supplied attribute names in LDAP Compare requests, combining LDAP filter injection with improper authorization checks. This allows authenticated low-privilege users to execute internal database searches in a trusted context, bypassing ACL enforcement and disclosing confidential attributes like msKds-RootKeyData that can be leveraged to derive gMSA passwords offline.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm Samba AD DC is runningCheck smb.conf for 'server role = active directory domain controller' or look for smbd, winbindd, and samba processes running as domain controllerAffected if Samba is configured and running as an Active Directory Domain Controller
-
Check Samba versionRun 'samba --version' or 'smbd -V' to get the installed Samba versionAffected if The installed version is older than the patched version for CVE-2026-58222 (version comparison required against vendor advisories)
-
Verify if gMSAs exist in the environmentRun LDAP query for objects with objectClass=msDS-ManagedServiceAccount or check AD for gMSA accounts using ldp.exe or ldapsearchAffected if Group Managed Service Accounts exist in the AD domain (the vulnerability targets msKds-RootKeyData which is used for gMSA password generation)
-
Test low-privilege user LDAP compare accessUsing an authenticated low-privilege test account, perform an LDAP compare operation requesting the msKds-RootKeyData attribute against a domain objectAffected if A low-privilege authenticated user can successfully read msKds-RootKeyData via LDAP compare (this indicates ACL bypass)
-
Audit LDAP permissions on msKds-RootKeyDataCheck ACLs on the msKds-RootKeyData attribute in AD using dsacls or ldapsearch with proper admin credentials to verify expected access restrictionsAffected if The attribute shows permissions allowing read access by non-privileged users, or permissions appear to be bypassed
If Samba AD DC is running with a version lacking the CVE-2026-58222 patch AND gMSAs exist in the environment AND low-privilege users can read msKds-RootKeyData via LDAP compare, the environment is vulnerable to domain compromise through gMSA password derivation.
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 dataApply Samba security patches when available; restrict LDAP Compare permissions to prevent low-privilege users from accessing sensitive attributes; audit for unauthorized attribute enumeration and gMSA key exposure.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58222 — 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-58222 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