dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-22536

HIGH · 8.6 CVSS v4.0 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
The absence of permissions control for the user XXX allows the current configuration in the sudoers file to escalate privileges without any restrictions

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 confidence

The vulnerability involves improper sudoers configuration where a user (referred to as XXX) is granted unrestricted sudo privileges without proper permission controls, allowing complete privilege escalation to root without constraints.

MitigationReview and restrict the sudoers configuration to enforce least-privilege principles by limiting allowed commands and requiring proper authentication, removing any NOPASSWD entries that grant unrestricted access.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if user XXX exists on the system
    Run 'id XXX' or 'getent passwd XXX' to check if the user account exists
    Affected if The user XXX account exists on the system and may have sudo access
  2. Locate sudoers configuration files
    Check /etc/sudoers and any files in /etc/sudoers.d/ directory using 'ls -la /etc/sudoers /etc/sudoers.d/'
    Affected if Sudoers configuration files are present and readable by root
  3. Search for user XXX in sudoers configuration
    Use 'grep -r "XXX" /etc/sudoers /etc/sudoers.d/' or 'visudo -l 2>/dev/null' to find entries for user XXX
    Affected if An entry for user XXX is found in any sudoers file
  4. Check for unrestricted root access permissions
    Examine the sudoers entry for user XXX - look for (ALL) ALL, (ALL) NOPASSWD: ALL, or similar patterns that grant full root access without command restrictions
    Affected if User XXX has (ALL) ALL or (ALL) NOPASSWD: ALL without specific command restrictions
  5. Verify current sudo access for user XXX
    As root or using an authorized account, run 'sudo -l -U XXX' to list the effective sudo permissions for user XXX
    Affected if The output shows user XXX can run any command as any user without restrictions

A user is affected if user XXX exists and has an unrestricted sudoers entry granting (ALL) ALL or (ALL) NOPASSWD: ALL without command constraints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and restrict the sudoers configuration to enforce least-privilege principles by limiting allowed commands and requiring proper authentication, removing any NOPASSWD entries that grant unrestricted access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22536 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22536 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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