Skip to content
Fencer Intel
high 8.1

CVE-2026-90959 json

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

published last mo. modified 8d ago also EUVD-2026-85920

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9 0:3.49.71-1.el9ap
  • Red Hat Red Hat Ansible Automation Platform 2.6 1791947385
  • Red Hat Red Hat Ansible Automation Platform 2.7 1792388670

Is CVE-2026-90959 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-90959 updated cvss 8.1

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

  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-25/hub-rhel8
    affected: workaround, no fix planned “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.”
  • Red Hat Satellite 6 python-pulpcore, python3-pulpcore, python3.12-pulpcore Red Hat Update Infrastructure 5 rhui5/rhua-rhel9
    affected: workaround, no fix available “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.”
  • Red Hat Ansible Automation Platform 2.6 ansible-automation-platform-26/hub-rhel9 1791947385
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.” RHSA-2026:87120
  • Red Hat Ansible Automation Platform 2.6 for RHEL 9 python3.12-pulpcore 3.49.71-1.el9ap
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.” RHSA-2026:87004
  • Red Hat Ansible Automation Platform 2.7 ansible-automation-platform-27/hub-rhel9 1792388670
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.” RHSA-2026:87124
  • Red Hat Ansible Automation Platform 2 python-pulpcore, pulpcore-selinux, python3x-pulpcore, python3.11-pulpcore, ansible-automation-platform-24/hub-rhel8 Red Hat Ansible Automation Platform 2.6 ansible-automation-platform-26/gateway-rhel9 1791971533, ansible-automation-platform-26/hub-web-rhel9 1791952205, ansible-automation-platform-26/receptor-rhel9 1791968536, ansible-automation-platform-26/mcp-tools-rhel9 1791941340, ansible-automation-platform-26/controller-rhel9 1791947602, ansible-automation-platform-26/de-minimal-rhel9 1791961810, +24 more Red Hat Ansible Automation Platform 2.6 for RHEL 9 receptor 1.6.9-1.el9ap, molecule 26.10.0-1.el9ap, receptorctl 1.6.9-1.el9ap, ansible-lint 26.10.1-1.el9ap, ansible-rulebook 1.2.3-1.el9ap, automation-hub 4.11.15-1.el9ap, +51 more Red Hat Ansible Automation Platform 2.6 for RHEL 10 receptor 1.6.9-1.el10ap, molecule 26.10.0-1.el10ap, python-cffi 2.0.0-2.el10ap, receptorctl 1.6.9-1.el10ap, python3-cffi 2.0.0-2.el10ap, ansible-lint 26.10.1-1.el10ap, +11 more Red Hat Ansible Automation Platform 2.7 ansible-automation-platform-27/gateway-rhel9 1792429216, ansible-automation-platform-27/hub-web-rhel9 1792394496, ansible-automation-platform-27/receptor-rhel9 1792139928, ansible-automation-platform-27/mcp-tools-rhel9 1792425046, ansible-automation-platform-27/controller-rhel9 1792389457, ansible-automation-platform-27/de-minimal-rhel9 1792141111, +26 more Red Hat Satellite 6 pulpcore-selinux, rubygem-pulpcore_client, pulpcore-obsolete-packages
    +2 more products
    Red Hat Update Infrastructure 4 for Cloud Providers python-pulpcore, pulpcore-selinux, python-pulpcore-client Red Hat Update Infrastructure 5 rhui5/rhua-tp-rhel9, python-pulpcore-client
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9
  • Red Hat Red Hat Ansible Automation Platform 2.6
  • Red Hat Red Hat Ansible Automation Platform 2.7
  • Red Hat Red Hat Ansible Automation Platform 2
  • Red Hat Red Hat Satellite 6
  • Red Hat Red Hat Update Infrastructure 4 for Cloud Providers
  • Red Hat Red Hat Update Infrastructure 5

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.