# CVE-2025-49521: Event-driven-ansible: template injection via git branch and refspec in eda projects

> Authenticated users can inject Jinja2 templates via Git branch values to execute commands or steal tokens on EDA workers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 30 Jun 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-g6ph-9xfv-87c2

## What is CVE-2025-49521?

CVE-2025-49521 is a high-severity code injection vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 30 Jun 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 EDA component of the Ansible Automation Platform, where user-supplied Git branch or refspec values are evaluated as Jinja2 templates. This vulnerability allows authenticated users to inject expressions that execute commands or access sensitive files on the EDA worker. In OpenShift, it can lead to service account token theft.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

Apply the vendor's patch.

## Is CVE-2025-49521 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49521 is a high-severity code injection vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 30 Jun 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-49521 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-49521/ (Markdown: https://insights.sbomify.com/CVE-2025-49521/index.md)
```

## Sources

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

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