CVE-2026-90959

Pulpcore: pulpcore: file:// scheme allowlist bypass in content upload file_url field enables arbitrary file read and pulp container registry signing key theft

HIGH
8.1
CVSS Score
Published: September 24, 2026 at 02:49 PM UTC
Updated: October 21, 2026 at 07:17 PM UTC
3 products affected across 1 vendorSatelliteAnsible Automation PlatformUpdate Infrastructure

Using Red Hat Ansible Automation Platform 2 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Ansible Automation Platform 2 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions2
Vendor states this is fixed in 0:3.49.71-1.el9ap (unaffected)
Vendor states this is fixed in 1791947385 (unaffected)
Vendor states this is fixed in 1792388670 (unaffected)
Vendor states this is fixed in 2 (unaffected)
All versions6
Vendor states this is fixed in 6 (unaffected)
All versions5
Vendor states this is fixed in 4 (unaffected)
Vendor states this is fixed in 5 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (5)

VDB Entryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/security/cve/CVE-2026-90959
Issue Trackingx_refsource_REDHAT
Source: cverecord
https://bugzilla.redhat.com/show_bug.cgi?id=2533037
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:87004
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:87120
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:87124

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHredhat
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card