# CVE-2025-5988: Aap-gateway: csrf origin checking is disabled

> Attackers can bypass CSRF origin checks in Ansible aap-gateway, potentially forcing actions on external components like controller or hub.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 4 Aug 2025
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-w8g9-rc94-7pq8

## What is CVE-2025-5988?

CVE-2025-5988 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Ansible aap-gateway. Cross-site request forgery (CSRF) origin checking is not done on requests from the gateway to external components, such as the controller, hub, and eda.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-5988?


## How do I fix CVE-2025-5988?

Apply the vendor's patch.

## Is CVE-2025-5988 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5988 and fix it if it is affected.

What it is: CVE-2025-5988 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 4 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5988 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2.5 for RHEL 8. 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-2025-5988/ (Markdown: https://insights.sbomify.com/CVE-2025-5988/index.md)
```

## Sources

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

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