{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90959 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90959 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90959 is a high-severity path traversal vulnerability in Red Hat Ansible Automation Platform 2, published on 24 Sep 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-90959 and fix it if it is affected.\n\nWhat it is: CVE-2026-90959 is a high-severity path traversal vulnerability in Red Hat Ansible Automation Platform 2, published on 24 Sep 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-90959 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-90959/ (Markdown: https://insights.sbomify.com/CVE-2026-90959/index.md)","id":"CVE-2026-90959","markdown":"https://insights.sbomify.com/CVE-2026-90959/index.md","name":"CVE-2026-90959","record":{"aliases":["GHSA-mfxv-9hc5-3jv3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Pulp content management","requires_auth":"low_privilege","summary":"Authenticated users can bypass file URL validation to read arbitrary server files, potentially stealing container registry signing keys to forge access tokens.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A path traversal vulnerability was found in pulpcore. The content upload API accepts a 'file_url' parameter that allows users with file repository privileges to specify a local file URL for Pulp to download and store. A URL scheme validation check uses a string prefix comparison that only rejects URLs beginning with 'file://', but Python's URL parser recognizes the 'file:' scheme without double slashes, creating a mismatch between what is validated and what is dispatched to the file downloader. An authenticated user with low-privilege repository permissions can supply a specially crafted URL using relative path traversal sequences to read any file accessible to the Pulp server process. In deployments that include Pulp Container, successful exploitation allows an attacker to read the container registry token signing private key and forge bearer tokens, granting unauthorized access to all private container repositories in the affected registry.","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":"Path traversal in Red Hat Ansible Automation Platform 2","id":"CVE-2026-90959","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"MISP LdapAuth and LinOTPAuth Authentication Bypass via Empty or Non-String Credentials","id":"CVE-2026-90961"},"packages":[],"prev":{"headline":"MISP: Stored XSS via Inline-Served SVG Organisation Logos and Report Pictures","id":"CVE-2026-90957"},"products":["Red Hat Ansible Automation Platform 2","Red Hat Ansible Automation Platform 2.6","Red Hat Ansible Automation Platform 2.6 for RHEL 9","Red Hat Ansible Automation Platform 2.7","Red Hat Satellite 6","Red Hat Update Infrastructure 4 for Cloud Providers","Red Hat Update Infrastructure 5"],"published":"2026-09-24","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":"total"},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Red Hat"]},"summary":"Authenticated users can bypass file URL validation to read arbitrary server files, potentially stealing container registry signing keys to forge access tokens.","url":"https://insights.sbomify.com/CVE-2026-90959/"}