cve.bz

CVE-2026-103868

6.5 mediumEPSS 0.2%

Medium (6.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in pulp-container when it authenticates to an upstream registry. Basic and bearer credentials from one remote are reused for later downloads in the same worker. A user who can sync a container remote, and can point that remote at a server they control, receives the username, password, or bearer token stored for a different remote, and can reuse that credential at the upstream registry. Content stored in Pulp is not changed, and the service is not stopped.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th 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-488 Exposure of Data Element to Wrong Session
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-103868 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103868?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103868?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-103868 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.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate by Red Hat Product Security. This vulnerability affects pulp-container's authenticated download from container remotes.

The caller here must already be allowed to sync a container remote and to set its URL. The API keeps those credentials write-only, so the sync is how another account obtains them. Once any authenticated sync has filled the worker, a later sync reads the cache at will. That is not a race.

The caller needs container.sync_containerrepository and the ability to set the remote URL. No other setting is required. A deployment that never syncs an authenticated container remote has nothing stored to disclose. The cache is process-wide, including across Pulp domains, and it remains until the worker exits.

This is a separate CVE from the `pulp-ansible` token cache **(CVE-2026-103869)**. A different repository and independently fixable.

```

The shared cache code was added in `pulp-container 1.3.0`.

```

```

RHUI ships this code, and an RHUI admin can type a registry URL when adding a container. Pulp here runs on a separate node, only that admin can reach it. End users have no path to the sync API. The admin who can reach it already configures those registry credentials and administers the node. That is not the same exposure as a Pulp user who can sync but does not already hold the credential. Hence, it is not affected because Vulnerable Code cannot be Controlled by Adversary.

Additionally, RHUI's container API client packages do not run the downloader. It does not contain `RegistryAuthHttpDownloader`. Hence, it is not affected.

```

Red Hat's mitigation

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 Ansible Automation Platform 2ansible-automation-platform-24/hub-rhel8Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/hub-rhel8Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/hub-rhel9Affected
Red Hat Ansible Automation Platform 2python3.11-pulp-containerNot affected
Red Hat Ansible Automation Platform 2python3.12-pulp-containerNot affected
Red Hat Ansible Automation Platform 2python3x-pulp-containerNot affected
Red Hat Ansible Automation Platform 2python-pulp-containerNot affected
Red Hat Satellite 6python3.12-pulp-containerAffected
Red Hat Satellite 6python-pulp-containerAffected
Red Hat Update Infrastructure 4 for Cloud Providerspython-pulp-containerNot affected
Red Hat Update Infrastructure 4 for Cloud Providerspython-pulp-container-clientNot affected
Red Hat Update Infrastructure 5python-pulp-container-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-103868.

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High

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

References

Check your stackJSON