{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71365 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-71365 is a high-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 18 Aug 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-71365 and fix it if it is affected.\n\nWhat it is: CVE-2026-71365 is a high-severity server-side request forgery vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8, published on 18 Aug 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-71365 in the wild and no public exploit code.\n\nAffected product: Red Hat Ansible Automation Platform 2.5 for RHEL 8. 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-71365/ (Markdown: https://insights.sbomify.com/CVE-2026-71365/index.md)","id":"CVE-2026-71365","markdown":"https://insights.sbomify.com/CVE-2026-71365/index.md","name":"CVE-2026-71365","record":{"aliases":["GHSA-89hq-rjv2-rxvp"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Ansible Automation Platform","requires_auth":"low_privilege","summary":"An admin can forge webhook payloads to trigger SSRF, leaking Git Personal Access Tokens to attacker-controlled endpoints.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected Git provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured Git Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Awx: webhook status callback ssrf leaks the git pat","id":"CVE-2026-71365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Awx: notification backends allow ssrf and credential leakage","id":"CVE-2026-71366"},"packages":[],"prev":{"headline":"Awx: project archive extraction allows path traversal file writes","id":"CVE-2026-71364"},"products":["Red Hat Ansible Automation Platform 2.5 for RHEL 8","Red Hat Ansible Automation Platform 2.5 for RHEL 9","Red Hat Ansible Automation Platform 2.6","Red Hat Ansible Automation Platform 2.6 for RHEL 9","Red Hat Ansible Automation Platform 2.7"],"published":"2026-08-18","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-08-25","vendors":["Red Hat"]},"summary":"An admin can forge webhook payloads to trigger SSRF, leaking Git Personal Access Tokens to attacker-controlled endpoints.","url":"https://insights.sbomify.com/CVE-2026-71365/"}