CVE-2026-103868

Pulp-container: registry credentials are reused across remotes in a worker

  • Medium 6.5

Description

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.

Key facts

Published
7 Oct 2026
Last changed
14 Oct 2026
Assigned by
redhat
EPSS
0.227% likely to be exploited in the next 30 days, higher than 13.583% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.5CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

What to do

  • 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.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: affected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Ansible Automation Platform 2
  • Default status: unaffected
Red HatRed Hat Satellite 6
  • Default status: affected
Red HatRed Hat Satellite 6
  • Default status: affected
Red HatRed Hat Update Infrastructure 4 for Cloud Providers
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 4 for Cloud Providers
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected
Red HatRed Hat Update Infrastructure 5
  • Default status: unaffected

Timeline

  1. 1 Oct 2026 Reported to Red Hat.
  2. 7 Oct 2026 Made public.
  3. 7 Oct 2026 Published

Weakness

References