# CVE-2026-79678: Code injection in Red Hat Enterprise Linux 10

> Authenticated users can exploit eval() in idp-add to read server environment variables and cause denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-79678, GHSA-2rwh-2wx9-4qwh, UBUNTU-CVE-2026-79678

## What is CVE-2026-79678?

CVE-2026-79678 is a high-severity code injection vulnerability in Red Hat Enterprise Linux 10, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in FreeIPA's idp-add command, where insufficiently validated --organization/--base-url input reaches a constrained eval() call before the corresponding LDAP access control check is enforced. This allows any authenticated IPA principal, regardless of privilege level, to enumerate and read the environment variables of the affected server process and to cause denial of service via memory exhaustion.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-79678?


## How do I fix CVE-2026-79678?

Apply the vendor's patch.

## Is CVE-2026-79678 being exploited?

There is no known exploitation of CVE-2026-79678 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-79678 and fix it if it is affected.

What it is: CVE-2026-79678 is a high-severity code injection vulnerability in Red Hat Enterprise Linux 10, published on 7 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79678 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-79678/ (Markdown: https://insights.sbomify.com/CVE-2026-79678/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-79678
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-79678
- OSV: https://osv.dev/vulnerability/CVE-2026-79678

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-79678/
Summaries are generated and may contain mistakes; the official description above is the record.