# CVE-2026-79717: Galaxy_ng: galaxy_ng: blind ssrf via namespace avatar_url with no private-address restriction

> Authenticated users can trigger SSRF via namespace avatar URLs to probe internal networks and cause denial of service by pinning workers.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-86r5-w5c4-h244

## What is CVE-2026-79717?

CVE-2026-79717 is a medium-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A server-side request forgery (SSRF) vulnerability was found in galaxy_ng, the Ansible Galaxy server plugin for Pulp. An authenticated user with namespace management permissions can set a namespace avatar URL to an arbitrary address, including internal networks, loopback, or cloud instance metadata endpoints. A background worker fetches that URL without checking the destination, which lets the attacker probe internal services and enumerate reachable IP addresses. The HTTP client is also configured without an overall timeout, so a slow or non-responsive target can pin workers and cause a denial of service.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-79717 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79717 is a medium-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79717 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-79717/ (Markdown: https://insights.sbomify.com/CVE-2026-79717/index.md)
```

## Sources

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

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