PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-104034 Red Hat CVE debrief

A use-after-free vulnerability exists in the Kerberos Credential Manager (KCM) responder during Kerberos ticket-granting ticket (TGT) renewal. An authenticated local user with a renewable Kerberos ticket can trigger this issue on systems configured with KCM renewal, causing the KCM responder service to crash and resulting in a Denial of Service (DoS).

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

Who should care

Defenders responsible for systems configured with KCM renewal, especially those using Red Hat Enterprise Linux, should assess exposure and prioritize patching. This includes system administrators, security teams, and vulnerability management teams who need to verify affected systems, review vendor guidance, and implement patching and mitigation strategies to prevent potential crashes and ensure system availability.

Why it matters

Defenders should care about CVE-2026-104034 because it can lead to a Denial of Service (DoS) attack on systems configured with KCM renewal. Verification of affected systems, prioritization of patching, and monitoring of KCM responder service are crucial to prevent potential crashes and ensure system availability.

  • Potential Denial of Service (DoS) attacks
  • Verification of affected systems and KCM renewal configuration
  • Prioritization of patching to prevent potential crashes

Technical summary

A use-after-free vulnerability exists in the Kerberos Credential Manager (KCM) responder during Kerberos ticket-granting ticket (TGT) renewal. An authenticated local user with a renewable Kerberos ticket can trigger this issue on systems configured with KCM renewal, causing the KCM responder service to crash and resulting in a Denial of Service (DoS). The vulnerability affects systems using Red Hat Enterprise Linux with KCM renewal configured. Defenders should prioritize verifying affected systems and updating to patched versions to prevent potential DoS attacks.

Defensive priority

Defenders should prioritize verifying affected systems, especially those with KCM renewal configured, and update to patched versions to prevent potential DoS attacks.

Recommended defensive actions

  • Verify if systems are configured with KCM renewal and prioritize patching
  • Update to patched versions of sssd
  • Monitor KCM responder service for potential crashes
  • 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 Program record and NVD vulnerability detail provide information on the vulnerability. Red Hat has a security advisory for this issue. Evidence is limited to public sources and may not reflect the full scope of affected systems or potential impacts. Defenders should verify affected systems and review vendor guidance for patching and mitigation strategies.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-104034 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-104034 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.