{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103869 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103869 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-103869 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-103869 in the wild and no public exploit code.\n\nAffected product: Red Hat Ansible Automation Platform 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-103869/ (Markdown: https://insights.sbomify.com/CVE-2026-103869/index.md)","id":"CVE-2026-103869","markdown":"https://insights.sbomify.com/CVE-2026-103869/index.md","name":"CVE-2026-103869","record":{"aliases":["GHSA-c5vx-cvpm-2hf5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ansible Automation Platform","requires_auth":"low_privilege","summary":"Attackers can steal bearer tokens from other remotes by controlling a sync target, allowing unauthorized access to external services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Pulp-ansible: bearer tokens are reused across remotes in a worker","id":"CVE-2026-103869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Pulp-rpm: distribution tree publish creates directories from .treeinfo ids","id":"CVE-2026-103870"},"packages":[],"prev":{"headline":"Pulp-container: registry credentials are reused across remotes in a worker","id":"CVE-2026-103868"},"products":["Red Hat Ansible Automation Platform 2","Red Hat Satellite 6"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["Red Hat"]},"summary":"Attackers can steal bearer tokens from other remotes by controlling a sync target, allowing unauthorized access to external services.","url":"https://insights.sbomify.com/CVE-2026-103869/"}