Pulpcore: pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary file read and pulp container registry signing key theft
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
A path traversal vulnerability was found in pulpcore. The content upload API accepts a 'file_url' parameter that allows users with file repository privileges to specify a local file URL for Pulp to download and store. A URL scheme validation check uses a string prefix comparison that only rejects URLs beginning with 'file://', but Python's URL parser recognizes the 'file:' scheme without double slashes, creating a mismatch between what is validated and what is dispatched to the file downloader. An authenticated user with low-privilege repository permissions can supply a specially crafted URL using relative path traversal sequences to read any file accessible to the Pulp server process. In deployments that include Pulp Container, successful exploitation allows an attacker to read the container registry token signing private key and forge bearer tokens, granting unauthorized access to all private container repositories in the affected registry.
Text from CVE List
Affected versions 3
- Red Hat Ansible Automation Platform 2.6 for RHEL 9unaffected: 0:3.49.71-1.el9ap and laterCVE List
- Red Hat Ansible Automation Platform 2.6unaffected: 1791947385 and laterCVE List
- Red Hat Ansible Automation Platform 2.7unaffected: 1792388670 and laterCVE List
References 5
- access.redhat.com/errata/RHSA-2026:87004Advisoryvia CVE List
- access.redhat.com/errata/RHSA-2026:87120Advisoryvia CVE List
- access.redhat.com/errata/RHSA-2026:87124Advisoryvia CVE List
- access.redhat.com/security/cve/CVE-2026-90959Advisoryvia CVE List
- bugzilla.redhat.com/show_bug.cgi?id=2533037Referencevia CVE List