dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2026-6245

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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.

NVD · unedited
A flaw was found in the System Security Services Daemon (SSSD). The pam_passkey_child_read_data() function within the PAM passkey responder fails to properly handle raw bytes received from a pipe. Because the data is treated as a NUL-terminated C string without explicit termination, it results in an out-of-bounds read when processed by functions like snprintf(). A local attacker could potentially trigger this vulnerability by initiating a crafted passkey authentication request, causing the SSSD PAM responder to crash, resulting in a local Denial of Service (DoS).

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.

dbcve analysis · high confidence

The SSSD PAM passkey responder contains an out-of-bounds read vulnerability in the pam_passkey_child_read_data() function. The function improperly handles raw bytes received from a pipe by treating them as a NUL-terminated C string without explicit termination, causing out-of-bounds reads when processed by functions like snprintf(). A local attacker can trigger this by initiating a crafted passkey authentication request, causing the SSSD PAM responder to crash.

MitigationUpgrade to the patched SSSD version that properly NUL-terminates data read from pipes in the PAM passkey responder, or disable passkey authentication in SSSD if upgrade is not immediately feasible.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
SssdApplication
Affected:all versions

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.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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.

dbcve checks

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

  1. Confirm SSSD installation and version
    Run `rpm -q sssd` or `dpkg -l sssd` to check if SSSD is installed. Use `sssd --version` or check the package version to identify the installed release.
    Affected if SSSD is installed and the version is older than the patched release that addresses CVE-2026-6245
  2. Verify passkey responder is enabled
    Inspect /etc/sssd/sssd.conf for any [passkey] section or passkey-related configuration entries. Also check if passkey is listed in the services array under [sssd].
    Affected if A [passkey] section exists in sssd.conf or passkey is configured as an active service
  3. Check if passkey authentication is in use
    Review /etc/sssd/sssd.conf for passkey authentication configuration such as pam_passkey服务 or any passkey-related PAM stack configuration in /etc/pam.d/ files.
    Affected if Passkey authentication is configured or enabled as an authentication method in the SSSD PAM configuration
  4. Look for crash indicators
    Check system logs (journalctl, /var/log/messages, /var/log/secure) for SSSD PAM responder crashes related to passkey authentication around the time of attempted authentication.
    Affected if The PAM responder has crashed or produced errors involving pam_passkey_child_read_data when processing passkey requests

If SSSD with an unpatched version is installed, the passkey responder is enabled, and passkey authentication is configured, the environment is vulnerable to CVE-2026-6245.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the patched SSSD version that properly NUL-terminates data read from pipes in the PAM passkey responder, or disable passkey authentication in SSSD if upgrade is not immediately feasible.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6245 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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