CVE-2026-104033

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory published 2026-10-06. The CNA's CVSS baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-92890 (ENISA EUVD) · GHSA-v9m6-j2qm-86p2 (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A flaw was found in SSSD. When configured to enforce account expiration using LDAP (Lightweight Directory Access Protocol) shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass access controls and authenticate to the system. This allows unauthorized access to persist after the account was intended to be deactivated.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated Oct 6, 2026
No fix on record yet. Sources: redhat.
Red Hat

2479271 – (CVE-2026-104033) CVE-2026-104033 sssd: sssd: Access control bypass via improper LDAP shadow expiration check

https://bugzilla.redhat.com/show_bug.cgi?id=2479271
Red HatMentions a patch (unverified)

CVE-2026-104033 - 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-104033

Vendor Advisories for CVE-2026-104033(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
sssd2.10.1-1 ... 2.9.5-5 (26 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sssd2.10.1-2 ... 2.13.1-3 (11 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-25 14:56 UTCEG score recompute
  10. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-18 05:09 UTCEG score recompute
  18. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-16 11:04 UTCEG score recompute
  21. 2026-10-16 11:04 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-12 16:40 UTCEG score recompute
Show 27 more
  1. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-12 04:55 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  3. 2026-10-11 20:15 UTCEG score recompute
  4. 2026-10-11 18:28 UTCEG score recompute
  5. 2026-10-11 15:01 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-11 03:01 UTCEG score recompute
  8. 2026-10-11 03:01 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-10 01:09 UTCEG score recompute
  11. 2026-10-10 01:09 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  12. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-08 23:18 UTCEG score recompute
  14. 2026-10-08 23:18 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  15. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-07 21:26 UTCEG score recompute
  18. 2026-10-07 21:26 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  19. 2026-10-07 20:25 UTCEG score recompute
  20. 2026-10-07 20:25 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  21. 2026-10-07 17:24 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  22. 2026-10-06 15:32 UTCEG score recompute
  23. 2026-10-06 15:32 UTCGHSA enrichmentGHSA-v9m6-j2qm-86p2 · GitHub CVSS 5.4
  24. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-06 01:33 UTCEG score recompute
  26. 2026-10-06 00:41 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  27. 2026-10-06 00:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-104033?
CVE-2026-104033 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. A flaw was found in SSSD. When configured to enforce account expiration using LDAP (Lightweight Directory Access Protocol) shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass…
When was CVE-2026-104033 made public?
CVE-2026-104033 was made public on October 5, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-104033 actively exploited?
CVE-2026-104033 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104033?
CVE-2026-104033 has a CVSS base score of 5.4 (the CNA's own assessment, by redhat; NVD's own analysis pending).
How do I remediate CVE-2026-104033?
No fix for CVE-2026-104033 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-104033 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-104033

Explore →

Is Your Infrastructure Affected by CVE-2026-104033?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.