cve.bz

CVE-2026-103870 Pulp-rpm: distribution tree publish creates directories from .treeinfo ids

5.0 mediumEPSS 0.3%Fix available

Medium (5.0) in red hat. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in pulp-rpm when it publishes a distribution tree. Addon and variant ids from .treeinfo are used as directory names. A user who can sync or upload that tree can make the publish task create a new directory outside the task work area and write that tree's repository metadata and packages there, as the Pulp worker user. An existing file or directory is not replaced. The flaw does not disclose data and does not stop the service.

Severity

CVSS 3.1

5.0 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat Satellite 6.16 for RHEL 8: fixed in 0:3.26.9-1.el8pc
  • Red Hat Red Hat Satellite 6.16 for RHEL 9: fixed in 0:3.26.9-1.el9pc
  • Red Hat Red Hat Satellite 6.17 for RHEL 9: fixed in 0:3.27.14-1.el9pc
  • Red Hat Red Hat Satellite 6.18 for RHEL 9: fixed in 0:3.29.12-1.el9pc
  • Red Hat Red Hat Satellite 6.19 for RHEL 9: fixed in 0:3.32.15-1.el9pc
  • Red Hat: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-103870 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103870?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103870?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103870 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • red hat:red hat satellite 6.16 for rhel 8
  • red hat:red hat satellite 6.16 for rhel 9
  • red hat:red hat satellite 6.17 for rhel 9
  • red hat:red hat satellite 6.18 for rhel 9
  • red hat:red hat satellite 6.19 for rhel 9
  • red hat:red hat update infrastructure 4 for cloud providers
  • red hat:red hat update infrastructure 5

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat Satellite 6.16 for RHEL 80:3.26.9-1.el8pc
Red Hat Satellite 6.16 for RHEL 90:3.26.9-1.el9pc
Red Hat Satellite 6.17 for RHEL 90:3.27.14-1.el9pc
Red Hat Satellite 6.18 for RHEL 90:3.29.12-1.el9pc
Red Hat Satellite 6.19 for RHEL 90:3.32.15-1.el9pc

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatsatellite:6.16::el8candlepin, candlepin-selinux0:4.4.26-2.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8foreman, foreman-cli, foreman-ec2 and 12 more0:3.12.0.26-1.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8rubygem-crass0:1.0.8-1.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8rubygem-katello0:4.14.0.24-1.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8rubygem-puma, rubygem-puma-debuginfo, rubygem-puma-debugsource0:6.4.3-2.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8rubygem-safemode0:1.5.0-3.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el8, satellite_capsule:6.16::el8python-pulp-rpm, python3.11-pulp-rpm0:3.26.9-1.el8pcRHSA-2026:99949
Red Hatsatellite:6.16::el8, satellite_capsule:6.16::el8python-pulpcore, python3.11-pulpcore0:3.49.39-5.el8pcRHSA-2026:99949
Red Hatsatellite:6.16::el8, satellite_capsule:6.16::el8python-pyjwt, python3.11-pyjwt, python3.11-pyjwt+crypto0:2.15.1-1.el8pcRHSA-2026:99949
Red Hatsatellite:6.16::el8, satellite_capsule:6.16::el8python-pysequoia, python3.11-pysequoia0:0.1.35-1.el8pcRHSA-2026:99949
Red Hatsatellite:6.16::el8, satellite_capsule:6.16::el8rubygem-smart_proxy_dynflow0:0.9.3-2.el8satRHSA-2026:99949
Red Hatsatellite:6.16::el9candlepin, candlepin-selinux0:4.4.26-2.el9satRHSA-2026:99949
68 more for Red Hat in the JSON and on Red Hat's page.

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated as Moderate by Red Hat Product Security. This vulnerability affects pulp-rpm's publication of kickstart distribution trees.

The caller needs an account that can put a distribution tree into a repository, which is rpm.sync_rpmrepository or the permission to upload RPM content. No extra setting is required. Publishing a repository version that contains a distribution tree is the normal kickstart path.

The write is limited because creation fails when the path already exists, and because parent directories are not created. The result is a new directory the worker user is allowed to create, not replacement of existing files.

```

This behavior was added with kickstart publishing in pulp-rpm 3.0.0b5

```

```

Default Red Hat repository sync uses mirror mode and does not run this directory creation. Custom upload syncs RPM files only, with no .treeinfo. Pulp is on a separate node, only the RHUI admin can reach it, and sync is from the Red Hat CDN almost all of the time. An end user cannot supply a distribution tree. Hence, it is not affected because Vulnerable Code cannot be Controlled by Adversary.

Additionally, RHUI's RPM API client packages does not publish distribution trees. Hence, they are not affected.

Note: Ansible Automation Platform does not ship pulp-rpm.

```

Red Hat's mitigation

Syncing distribution trees only from a trusted upstream avoids a crafted .treeinfo from that source. An account that can upload a tree directly can still supply the file.

Otherwise, Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when they become available.

ProductPackageStateAdvisory
Red Hat Satellite 6.16 for RHEL 8python-pulp-rpm-0:3.26.9-1.el8pcFixed 2026-11-12RHSA-2026:99949
Red Hat Satellite 6.16 for RHEL 9python-pulp-rpm-0:3.26.9-1.el9pcFixed 2026-11-12RHSA-2026:99949
Red Hat Satellite 6.17 for RHEL 9python-pulp-rpm-0:3.27.14-1.el9pcFixed 2026-11-12RHSA-2026:99950
Red Hat Satellite 6.18 for RHEL 9python3.12-pulp-rpm-0:3.29.12-1.el9pcFixed 2026-11-12RHSA-2026:99952
Red Hat Update Infrastructure 4 for Cloud Providerspython-pulp-rpmNot affected
Red Hat Update Infrastructure 4 for Cloud Providerspython-pulp-rpm-clientNot affected
Red Hat Update Infrastructure 5python-pulp-rpm-clientNot affected
Red Hat Update Infrastructure 5rhui5/rhua-rhel9Not affected
Red Hat Update Infrastructure 5rhui5/rhua-tp-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103870.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON