Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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

HighCVSS 8.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 32/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: automation-gateway-server (Red Hat:ansible_automation_platform:2.6::el9) 0:2.6.20261019-1.el9ap; automation-platform-ui (Red Hat:ansible_automation_platform:2.6::el9) 0:2.6.15-1.el9ap; python3.12-pulpcore (Red Hat:ansible_automation_platform:2.6::el9) 0:3.49.71-1.el9ap.

Low priority for now. Upgrade to automation-gateway-server (Red Hat:ansible_automation_platform:2.6::el9) 0:2.6.20261019-1.el9ap; automation-platform-ui (Red Hat:ansible_automation_platform:2.6::el9) 0:2.6.15-1.el9ap; python3.12-pulpcore (Red Hat:ansible_automation_platform:2.6::el9) 0:3.49.71-1.el9ap or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 24, 2026
Updated
Nov 13, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
8.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-90959

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat Red Hat Ansible Automation Platform 2

    • all versionsunknown
    • all versionsaffected
    • all versionsunknown
    • all versionsunknown
    • all versionsunknown
    • all versionsunknown
  • Red Hat Red Hat Ansible Automation Platform 2.6

    • 1791947385 and laternot affected · rpm
  • Red Hat Red Hat Ansible Automation Platform 2.6 for RHEL 9

    • 0:3.49.71-1.el9ap and laternot affected · rpm
  • Red Hat Red Hat Ansible Automation Platform 2.7

    • 1792388670 and laternot affected · rpm
  • Red Hat Red Hat Satellite 6

    • all versionsunknown
    • all versionsunknown
    • all versionsunknown
  • Red Hat Red Hat Satellite 6.16 for RHEL 8

    • 0:3.49.39-5.el8pc and laternot affected · rpm
    • 0:3.49.39-5.el8pc and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.16 for RHEL 9

    • 0:3.49.39-5.el9pc and laternot affected · rpm
    • 0:3.49.39-5.el9pc and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.17 for RHEL 9

    • 0:3.63.21-4.el9pc and laternot affected · rpm
    • 0:3.63.21-4.el9pc and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.18 for RHEL 9

    • 0:3.73.45-1.el9pc and laternot affected · rpm
    • 0:3.73.45-1.el9pc and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.19 for RHEL 9

    • 0:3.85.35-1.el9pc and laternot affected · rpm
    • 0:3.85.35-1.el9pc and laternot affected · rpm
  • Red Hat Red Hat Update Infrastructure 4 for Cloud Providers

    • all versionsunknown
    • all versionsunknown
    • all versionsunknown
  • Red Hat Red Hat Update Infrastructure 5

    • all versionsunknown
    • all versionsaffected
    • all versionsunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:ansible_automation_platform:2.6::el9automation-gateway-serverbefore 0:2.6.20261019-1.el9ap0:2.6.20261019-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-platform-uibefore 0:2.6.15-1.el9ap0:2.6.15-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9python3.12-pulpcorebefore 0:3.49.71-1.el9ap0:3.49.71-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9python3.12-pyjwtbefore 0:2.14.0-1.el9ap0:2.14.0-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9python3.12-pyjwt+cryptobefore 0:2.14.0-1.el9ap0:2.14.0-1.el9ap
Red Hat:satellite_capsule:6.19::el9createrepo_cbefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9createrepo_c-debuginfobefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9createrepo_c-debugsourcebefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9createrepo_c-libsbefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9createrepo_c-libs-debuginfobefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9foremanbefore 0:3.18.0.19-1.el9sat0:3.18.0.19-1.el9sat
Red Hat:satellite_capsule:6.19::el9foreman-debugbefore 0:3.18.0.19-1.el9sat0:3.18.0.19-1.el9sat
Red Hat:satellite_capsule:6.19::el9foreman-pcpbefore 0:3.18.0.19-1.el9sat0:3.18.0.19-1.el9sat
Red Hat:satellite_capsule:6.19::el9python3.12-createrepo_cbefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-createrepo_c-debuginfobefore 0:1.2.6-1.el9pc0:1.2.6-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pulp-containerbefore 0:2.26.19-2.el9pc0:2.26.19-2.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pulp-rpmbefore 0:3.32.15-1.el9pc0:3.32.15-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pulpcorebefore 0:3.85.35-1.el9pc0:3.85.35-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pyjwtbefore 0:2.15.1-1.el9pc0:2.15.1-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pyjwt+cryptobefore 0:2.15.1-1.el9pc0:2.15.1-1.el9pc
Red Hat:satellite_capsule:6.19::el9python3.12-pysequoiabefore 0:0.1.35-1.el9pc0:0.1.35-1.el9pc
Red Hat:satellite_capsule:6.19::el9rubygem-http-cookiebefore 0:1.1.6-2.el9sat0:1.1.6-2.el9sat
Red Hat:satellite_capsule:6.19::el9rubygem-smart_proxy_container_gatewaybefore 0:3.5.1-1.el9sat0:3.5.1-1.el9sat
Red Hat:satellite_capsule:6.19::el9rubygem-smart_proxy_dynflowbefore 0:1.0.0-3.el9sat0:1.0.0-3.el9sat

+27

Other highest-scoring records for the same primary product.

  • CVE-2026-44191Ansible-lightspeed: visual studio code ansible lightspeed extension: remote code execution via command injection in configuration settings
    31Monitor
  • CVE-2026-44190Ansible-lightspeed: ansible lightspeed visual studio code extension: arbitrary code execution via command injection in activation script setting
    31Monitor
  • CVE-2026-44189Ansible-lightspeed: visual studio code ansible lightspeed extension: arbitrary code execution via malicious playbook filename
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-92091Sep 16, 2026 · Jwcrypto: jwcrypto: denial of service via o(n^2) duplicate check on unbounded jwk key_ops array
    23Monitor
  • ← EarlierCVE-2026-94416Sep 24, 2026 · Aap-gateway: aap-gateway: authorization bypass via workload identity token forgery
    27Monitor
  • Later →CVE-2026-103754Oct 1, 2026 · Ansible-runner: ansible-runner: path traversal and symlink escape in unstream_dir() allows file write outside the target directory
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:foreman0:3.18.0.19-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:foreman-cli0:3.18.0.19-1.el9sat · Red Hat:satellite_utils:6.19::el9Package registry (OSV)
red hat:foreman-debug0:3.18.0.19-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:foreman-dynflow-sidekiq0:3.18.0.19-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-ec20:3.18.0.19-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-journald0:3.18.0.19-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-libvirt0:3.18.0.19-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-openstack0:3.18.0.19-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-pcp0:3.18.0.19-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:python3.12-pysequoia0:0.1.35-1.el9pc · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:rubygem-crass0:1.0.8-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:rubygem-katello0:4.20.0.12-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4419264 days apartAnsible-lightspeed: ansible lightspeed mcp server: remote code execution and data exfiltration via path traversal
    26Monitor
  • CVE-2026-1037547 days apartAnsible-runner: ansible-runner: path traversal and symlink escape in unstream_dir() allows file write outside the target directory
    23Monitor
  • CVE-2026-797059 days apartPodman: buildah: buildah/copier: directory escape via crafted tar symlinks when used outside buildah by non-root callers
    18Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2026-944160 days apartAap-gateway: aap-gateway: authorization bypass via workload identity token forgery
    27Monitor
  • CVE-2026-7136349 days apartAwx: unauthenticated debug endpoints trigger scheduler operations
    21Monitor

Not on record for this CVE: patch commit or PR link · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

References

All records