The vulnerability arises from improper validation of the 'file_url' parameter in the content upload API of pulpcore. The validation rejects URLs starting with 'file://', but Python's URL parser accepts 'file:' URLs without double slashes, allowing bypass of the check. An authenticated user with low privileges can craft a URL with relative path traversal sequences to read any file accessible by the Pulp server process. In environments with Pulp Container, this enables reading the container registry token signing private key, allowing forging of bearer tokens and unauthorized read/write access to private container repositories.

An attacker with low-privilege authenticated access can read arbitrary files on the Pulp server, potentially exposing sensitive data. In deployments with Pulp Container, the attacker can steal the registry JWT signing private key, forge bearer tokens, and gain unauthorized read and write access to all private container repositories in the affected registry. This results in a critical confidentiality and integrity breach. Availability impact is not indicated.

Red Hat currently states that no mitigation is available that meets their standards for usability, deployment, applicability, or stability. Users should monitor the Red Hat advisory for updates and apply any forthcoming official fixes once released. Until then, restricting access to the content upload API and limiting repository privileges may reduce risk but do not fully mitigate the vulnerability.