{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47660 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47660 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47660 is a high-severity server-side request forgery vulnerability in aehrc pathling, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47660 and fix it if it is affected.\n\nWhat it is: CVE-2026-47660 is a high-severity server-side request forgery vulnerability in aehrc pathling, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47660 in the wild and no public exploit code.\n\nAffected product: aehrc pathling. 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-47660/ (Markdown: https://insights.sbomify.com/CVE-2026-47660/index.md)","id":"CVE-2026-47660","markdown":"https://insights.sbomify.com/CVE-2026-47660/index.md","name":"CVE-2026-47660","record":{"aliases":["GHSA-245h-c573-9vr5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pathling Server","requires_auth":"none","summary":"Attackers can exfiltrate OAuth client credentials by supplying a malicious oauthMetadataUrl in bulk-submit operations, bypassing source validation.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Pathling is a set of tools that make it easier to use FHIR and clinical terminology within health data analytics. Prior to version 2.0.0 of Pathling Server, Pathling's bulk-submit operation allows an allowed submitter to supply an explicit `oauthMetadataUrl` parameter that is not validated against `pathling.bulkSubmit.allowableSources`. When present, the bulk-submit OAuth flow trusts metadata and the returned `token_endpoint` from the caller-chosen location, then builds outbound OAuth client authentication directly from the submitter's stored credentials. This is fixed in Pathling Server 2.0.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration","id":"CVE-2026-47660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Pathling has path traversal in $result endpoint that allows arbitrary warehouse file read","id":"CVE-2026-47661"},"packages":[],"prev":{"headline":"Pathling has path traversal in $import-pnp manifest that enables read-capable SSRF via /jobs/{jobId}/{filename}","id":"CVE-2026-47659"},"products":["pathling"],"published":"2026-08-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["aehrc"]},"summary":"Attackers can exfiltrate OAuth client credentials by supplying a malicious oauthMetadataUrl in bulk-submit operations, bypassing source validation.","url":"https://insights.sbomify.com/CVE-2026-47660/"}