Skip to content
statance
MenuClose
medium · CVSS 6.4

CVE-2026-79717

Galaxy_ng: galaxy_ng: blind ssrf via namespace avatar_url with no private-address restriction

Published 25 Aug 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

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.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
ansible-automation-platform-24/hub-rhel8Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-25/hub-rhel8Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-26/hub-rhel9Red HatDefault status: affectedSee vendor advisory
ansible-automation-platform-27/hub-rhel9Red HatDefault status: affectedSee vendor advisory
python3.11-galaxy-ngRed HatDefault status: affectedSee vendor advisory
python3.12-galaxy-ngRed HatDefault status: affectedSee vendor advisory
python3x-galaxy-ngRed HatDefault status: affectedSee vendor advisory
python-galaxy-ngRed HatDefault status: affectedSee 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.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. 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.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed