# CVE-2026-6494: Aap-mcp-server: aap mcp server: log injection allows social engineering attacks via unsanitized input

> An attacker can inject control characters into logs via unsanitized input, facilitating social engineering attacks against operators.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2026
- **Updated:** 18 Apr 2026
- **Also known as:** GHSA-c63q-7gvc-8xq3

## What is CVE-2026-6494?

CVE-2026-6494 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 17 Apr 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 the AAP MCP server. An unauthenticated remote attacker can exploit a log injection vulnerability by sending specially crafted input to the `toolsetroute` parameter. This parameter is not properly sanitized before being written to logs, allowing the attacker to inject control characters such as newlines and ANSI escape sequences. This enables the attacker to obscure legitimate log entries and insert forged ones, which could facilitate social engineering attacks, potentially leading to an operator executing dangerous commands or visiting malicious URLs.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

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


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

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

## Is CVE-2026-6494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6494 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 17 Apr 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-6494 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-6494/ (Markdown: https://insights.sbomify.com/CVE-2026-6494/index.md)
```

## Sources

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

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