CWE-23Weakness · CWE-23

CVE-2026-14476

HIGH · 8.0 CVSS v3.1 Published 2026-07-07

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

86/100

Remediation priority · High

Remotely reachable Zero-click 7 weeks old

Official description

NVD · unedited

A path traversal flaw was found in SSSD's AD GPO provider. The ad_gpo_extract_smb_components() function does not sanitize .. sequences in the gPCFileSysPath LDAP attribute, allowing an attacker with AD GPO management access to write files outside the GPO cache directory as root. On default RHEL configurations with SELinux enforcing, this can be used to inject Kerberos configuration leading to authentication bypass.

Technical summary

dbcve analysis · high confidence

A path traversal vulnerability exists in SSSD's AD GPO provider where the ad_gpo_extract_smb_components() function fails to sanitize '..' sequences in the gPCFileSysPath LDAP attribute. An attacker with AD GPO management privileges can write files outside the GPO cache directory as root, enabling injection of malicious Kerberos configuration and authentication bypass on RHEL systems with SELinux enforcing.

MitigationApply the SSSD security update that adds proper path sanitization for '..' sequences in the gPCFileSysPath attribute. Restrict AD GPO management access to trusted administrators and verify Kerberos configuration integrity after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Privileges: High
User interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

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

Check if SSSD is installed

Run 'rpm -q sssd' (RHEL/Fedora) or 'dpkg -l sssd' (Debian) to query the installed package. Alternatively, check '/etc/sssd/sssd.conf' exists.

Affected if SSSD is not installed - the system is not affected by this vulnerability.
Determine SSSD version

Run 'sssd --version' or 'rpm -q --qf "%{VERSION}-%{RELEASE}" sssd' to get the exact version number.

Affected if Unable to determine version - manually verify if your SSSD version is older than the patched release that addresses CVE-2026-14476.
Verify AD GPO provider is enabled

Inspect '/etc/sssd/sssd.conf' and look for 'ad_gpo' related options in the [domain/...] section, such as 'ad_gpo_cache_timeout', 'ad_gpo_refresh_timeout', or 'ad_gpo_send_server_timeout'. Also check for 'ad_gpo' in the services list.

Affected if No 'ad_gpo' options are configured - the AD GPO provider is not active and the system is likely not affected.
Confirm AD domain membership

Check for Active Directory integration using 'realm list' or verify '/etc/krb5.conf' contains your AD domain, or check 'net ads info' (if samba-client is installed).

Affected if System is not joined to an Active Directory domain - the GPO processing functionality is not in use.
Inspect GPO cache directory

Look for the SSSD GPO cache directory, typically located at '/var/lib/sss/gpo_cache/' or within the SSSD cache directory. Check if it exists and contains LDAP attribute data files.

Affected if No GPO cache directory exists - the system has not processed any AD GPOs and is likely not affected.

The system is affected only if SSSD with an unpatched version is installed, the AD GPO provider is enabled in sssd.conf, and the system processes Active Directory Group Policy Objects.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the SSSD security update that adds proper path sanitization for '..' sequences in the gPCFileSysPath attribute. Restrict AD GPO management access to trusted administrators and verify Kerberos configuration integrity after patching.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing8.0 h
Review / QA3.0 h

18.0 hours of engineering $3,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-14476 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-14476?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 8.0 High

Exploit likelihood EPSS, next 30 days 0.7%

Remediation

A high-priority fix

Have this fixed 18 hrs · Moderate

Typical engagement from $3,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-14476 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References