# CVE-2026-18141: Aap-gateway: aap-gateway: authentication bypass in event-driven ansible via forged http header

> Unauthenticated attackers can bypass mTLS authentication in Ansible Event-Driven Ansible by forging HTTP headers, allowing injection of arbitrary events to trigger workflows.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-9cwv-qxgx-ff4x

## What is CVE-2026-18141?

CVE-2026-18141 is a high-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in aap-gateway, a component of Ansible Automation Platform's Event-Driven Ansible (EDA). An unauthenticated remote attacker can bypass mutual Transport Layer Security (mTLS) authentication for event streams. This is achieved by manipulating the event stream URL and forging the HTTP Subject header. The system also inadvertently discloses the expected certificate subject in error messages, which simplifies the attack. This vulnerability allows an attacker to inject arbitrary events into EDA, potentially triggering automated workflows.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

Apply the vendor's patch.

## Is CVE-2026-18141 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18141 is a high-severity authentication bypass vulnerability in Red Hat Ansible Automation Platform 2, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18141 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-18141/ (Markdown: https://insights.sbomify.com/CVE-2026-18141/index.md)
```

## Sources

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

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