CVE-2026-103869: Red Hat Ansible Automation Platform 2 · Exposure of Data Element to Wrong Session
Affects Red Hat Ansible Automation Platform 2Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Ansible Automation Platform 2 | Affected– | Fixed in– |
| Red HatRed Hat Ansible Automation Platform 2 | Affected– | Fixed in– |
| Red HatRed Hat Satellite 6 | Affected– | Fixed in– |
AI-suggested
Until an official fix is available, avoid syncing Ansible remotes that use token refresh from untrusted or attacker-controlled servers.
Description
CVE-2026-103869 is a medium severity vulnerability in Red Hat Ansible Automation Platform 2 related to pulp-ansible's bearer-token refresh mechanism. The flaw causes an access token to be stored in a module-level variable and reused across different token downloads within the same worker. This allows a user who can sync an Ansible remote using token refresh and control the remote server to receive and reuse an access token intended for a different remote. The vulnerability does not alter stored content or disrupt the service.