PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-104035 Red Hat CVE debrief

A flaw in the Kerberos Credential Manager (KCM) responder of SSSD allows a local user to cause a Denial of Service (DoS) by maintaining a persistent connection and repeatedly storing and destroying credentials, leading to memory exhaustion. This issue arises because the service fails to release cached objects from memory when credentials are removed, causing continuous memory consumption growth and ultimately exhausting available memory, rendering the service unresponsive. System administrators and security teams should be aware of this vulnerability and take steps to mitigate it, especially in environments with high-risk exposure.

Vendor
Red Hat
Product
Red Hat Enterprise Linux 10
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-06
Original CVE updated
2026-10-08
Advisory published
2026-10-06
Advisory updated
2026-10-08

Who should care

System administrators and security teams responsible for managing SSSD installations, particularly in environments with high-risk exposure, should be aware of this vulnerability and take steps to mitigate it.

Why it matters

CVE-2026-104035 is a medium-severity vulnerability in SSSD's KCM responder that can lead to a Denial of Service (DoS) attack, causing system unresponsiveness due to memory exhaustion. System administrators and security teams should prioritize patching vulnerable systems to prevent potential exploitation.

  • Potential Denial of Service (DoS) attacks leading to system unresponsiveness
  • Memory exhaustion and resource depletion
  • Need for patching vulnerable systems to prevent exploitation

Technical summary

The vulnerability in SSSD's KCM responder allows a local user to cause a DoS by maintaining a persistent connection and repeatedly storing and destroying credentials, leading to memory exhaustion. The CVSS score for this vulnerability is 5.5, indicating a medium severity. This issue arises from the service's failure to release cached objects from memory when credentials are removed, causing continuous memory consumption growth. System administrators and security teams should prioritize patching vulnerable systems to prevent potential exploitation, especially in environments with high-risk exposure.

Defensive priority

System administrators and security teams should prioritize patching vulnerable systems, especially those with high-risk exposure, to prevent potential DoS attacks.

Recommended defensive actions

  • Patch vulnerable systems, especially those with high-risk exposure
  • Monitor system memory usage and KCM responder activity
  • Restrict access to sensitive systems and services
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected products. However, specific version information and exploitation details are not provided.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-104035 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-104035

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-104035 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-104035

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.