A flaw was found in SSSD. When configured with the LDAP access provider and ldap_access_order including ppolicy or lockout, a fail-open condition in the LDAP ppolicy access check can occur if a user lookup returns zero results. This can incorrectly return success and cache an allow decision, permitting continued authorization for a deleted or deprovisioned user. A remote attacker with prior valid account context could exploit this to maintain access to information and potentially make limited modifications to resources that should no longer be available.
CVE-2026-90462
Score 5.4 from GitHub Security Advisory published 2026-09-22. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 22, 2026
Advisory Details (2)
Auto-updated Sep 22, 20262479483 – (CVE-2026-90462) CVE-2026-90462 sssd: SSSD: Fail-open in LDAP ppolicy access check allows continued authorization
https://bugzilla.redhat.com/show_bug.cgi?id=2479483CVE-2026-90462 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-90462Vendor Advisories for CVE-2026-90462(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 21:59 UTCEG score recompute
- 2026-09-23 21:59 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 19:51 UTCEG score recompute
- 2026-09-22 19:51 UTCGHSA enrichment
- 2026-09-22 18:33 UTCEG score recompute
- 2026-09-22 17:37 UTCEG score recompute
- 2026-09-22 16:19 UTCEG score recompute
- 2026-09-22 15:55 UTCEG score recompute
- 2026-09-22 15:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-280
Frequently asked(5)
What is CVE-2026-90462?
When was CVE-2026-90462 disclosed?
Is CVE-2026-90462 actively exploited?
What is the CVSS score of CVE-2026-90462?
How do I remediate CVE-2026-90462?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90462
Is Your Infrastructure Affected by CVE-2026-90462?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.