{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47664 exists.","fix":"No fix has been published for CVE-2026-47664 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47664 is a high-severity server-side request forgery vulnerability in aehrc pathling, published on 7 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-47664 and fix it if it is affected.\n\nWhat it is: CVE-2026-47664 is a high-severity server-side request forgery vulnerability in aehrc pathling, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47664 exists.\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-47664/ (Markdown: https://insights.sbomify.com/CVE-2026-47664/index.md)","id":"CVE-2026-47664","markdown":"https://insights.sbomify.com/CVE-2026-47664/index.md","name":"CVE-2026-47664","record":{"aliases":["GHSA-69wc-hrxh-5528"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Health data analytics server","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit the $import-pnp operation to perform SSRF, leak credentials, and poison warehouse data by bypassing source allowlists.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-20","name":"Improper Input Validation"}],"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, the `$import-pnp` operation in Pathling Server accepts a caller-supplied `exportUrl` and uses it as the remote FHIR Bulk Export endpoint without constraining it to a trusted source. When PNP credentials are configured, Pathling builds a credentialed bulk-export client targeting the caller-chosen host, downloads manifest-selected files, and then reclassifies those staged files as trusted local `file://` imports - bypassing the configured `allowableSources` allowlist that protects the ordinary `$import` operation. This is fixed in Pathling Server 2.0.0. As a workaround, disable the `$import-pnp` operation (`pathling.operations.importPnpEnabled=false`) or do not configure PNP credentials.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Pathling: $import-pnp operation enables authenticated SSRF, credential leakage, and warehouse data poisoning","id":"CVE-2026-47664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Penpot: Stored XSS via comment content, innerHTML renders unsanitized HTML","id":"CVE-2026-47665"},"packages":[],"prev":{"headline":"Pathling: Typed CRUD/search/batch providers can lead to server-wide PHI exfiltration and cross-resource mutation","id":"CVE-2026-47663"},"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["aehrc"]},"summary":"Authenticated attackers can exploit the $import-pnp operation to perform SSRF, leak credentials, and poison warehouse data by bypassing source allowlists.","url":"https://insights.sbomify.com/CVE-2026-47664/"}