# CVE-2026-103869: Pulp-ansible: bearer tokens are reused across remotes in a worker

> Attackers can steal bearer tokens from other remotes by controlling a sync target, allowing unauthorized access to external services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-c5vx-cvpm-2hf5

## What is CVE-2026-103869?

CVE-2026-103869 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they control, receives an access token obtained for a different remote, and can reuse it at the service that issued it. Content stored in Pulp is not changed, and the service is not stopped.

Weakness: CWE-488 (Exposure of Data Element to Wrong Session)

## Which versions are affected by CVE-2026-103869?


## How do I fix CVE-2026-103869?

No fix has been published for CVE-2026-103869 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103869 being exploited?

There is no known exploitation of CVE-2026-103869 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103869 and fix it if it is affected.

What it is: CVE-2026-103869 is a medium-severity vulnerability in Red Hat Ansible Automation Platform 2, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103869 in the wild and no public exploit code.

Affected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103869/ (Markdown: https://insights.sbomify.com/CVE-2026-103869/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103869
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103869
- OSV: https://osv.dev/vulnerability/CVE-2026-103869

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103869/
Summaries are generated and may contain mistakes; the official description above is the record.