CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NMedium (6.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExplain CVE-2026-103869 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103869?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103869?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-103869 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 rates this Moderate.
This flaw has been rated as Moderate by Red Hat Product Security. The vulnerability affects pulp-ansible's bearer-token refresh for collection remotes.
The caller here must already be allowed to sync an Ansible remote configured for token refresh. The collection remote token is write-only on the API, so the sync is how another account obtains it. Once one refresh has filled the worker, a later sync reads the cache at will.
The caller needs ansible.sync_ansiblerepository on a remote that has both a token and an auth_url. That pair is the ordinary Galaxy and Automation Hub refresh-token configuration. No further setting is required. Remotes that do not refresh a token never enter this path. The stored token is process-wide, including across Pulp domains, and it remains until the worker exits.
```
The vulnerable global was added in pulp-ansible 0.6.0
```
It has same root cause as reported `pulp_container` finding **(CVE-2026-103868)**. This is a separate CVE from the pulp-container, as it has different codebase, and independently fixable.
```
Note: RHUI does not ship pulp-ansible.
```
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-24/hub-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-25/hub-rhel8 | Not affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-26/hub-rhel9 | Affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-27/hub-rhel9 | Affected | |
| Red Hat Ansible Automation Platform 2 | python3.11-pulp-ansible | Not affected | |
| Red Hat Ansible Automation Platform 2 | python3.12-pulp-ansible | Not affected | |
| Red Hat Ansible Automation Platform 2 | python3x-pulp-ansible | Not affected | |
| Red Hat Ansible Automation Platform 2 | python-pulp-ansible | Not affected | |
| Red Hat Satellite 6 | python3.12-pulp-ansible | Affected | |
| Red Hat Satellite 6 | python-pulp-ansible | 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-103869.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.