# CVE-2026-85475: Code injection in Red Hat Ansible Automation Platform 2

> Privileged users can inject rsyslog directives via log settings to execute arbitrary code and compromise the control plane.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-wpwh-486h-5v3j

## What is CVE-2026-85475?

CVE-2026-85475 is a high-severity code injection vulnerability in Red Hat Ansible Automation Platform 2, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the Ansible Automation Platform automation controller. The
external logging (rsyslog) configuration is generated by interpolating
user-controlled settings — LOG_AGGREGATOR_HOST, LOG_AGGREGATOR_MAX_DISK_USAGE_PATH
and LOG_AGGREGATOR_RSYSLOGD_ERROR_LOG_FILE — into an rsyslog RainerScript config
file without neutralizing RainerScript syntax. A privileged (superuser) user can
inject rsyslog directives, including an omprog action, causing arbitrary command
execution inside the control-plane rsyslog component. This allows disclosure of
the controller SECRET_KEY and database credentials, decryption of all stored
credentials, and full compromise of the control plane.

Weakness: CWE-96 (Improper Neutralization of Directives in Statically Saved Code)

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


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

No fix has been published for CVE-2026-85475 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85475 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85475 is a high-severity code injection vulnerability in Red Hat Ansible Automation Platform 2, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85475 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. 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-85475/ (Markdown: https://insights.sbomify.com/CVE-2026-85475/index.md)
```

## Sources

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

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