CVE-2026-79717
Galaxy_ng: galaxy_ng: blind ssrf via namespace avatar_url with no private-address restriction
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| ansible-automation-platform-24/hub-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-25/hub-rhel8Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-26/hub-rhel9Red Hat | Default status: affected | See vendor advisory |
| ansible-automation-platform-27/hub-rhel9Red Hat | Default status: affected | See vendor advisory |
| python3.11-galaxy-ngRed Hat | Default status: affected | See vendor advisory |
| python3.12-galaxy-ngRed Hat | Default status: affected | See vendor advisory |
| python3x-galaxy-ngRed Hat | Default status: affected | See vendor advisory |
| python-galaxy-ngRed Hat | Default status: affected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.