CVE-2026-47664

{"id": "CVE-2026-47664", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-47664", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-10T13:27:56.610772Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.6, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "aehrc", "product": "pathling", "versions": [{"status": "affected", "version": "< 2.0.0"}]}]}], "published": "2026-08-07T21:17:28.657", "references": [{"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-69wc-hrxh-5528", "source": "security-advisories@github.com"}, {"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-69wc-hrxh-5528", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-20"}, {"lang": "en", "value": "CWE-345"}, {"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Pathling es un conjunto de herramientas que facilitan el uso de FHIR y la terminolog\u00eda cl\u00ednica en el an\u00e1lisis de datos de salud. Antes de la versi\u00f3n 2.0.0 de Pathling Server, la operaci\u00f3n \u2019$import-pnp\u2019 en Pathling Server acepta una \u201cexportUrl\u201d proporcionada por el llamante y la utiliza como el punto final remoto de exportaci\u00f3n masiva (Bulk Export) de FHIR sin restringirla a una fuente de confianza. Cuando se configuran las credenciales PNP, Pathling construye un cliente de exportaci\u00f3n masiva (bulk-export) con credenciales dirigido al host elegido por el llamante, descarga archivos seleccionados por el manifiesto y luego reclasifica esos archivos preparados como importaciones locales de confianza \u201cfile: //\u201d - eludiendo la lista de permitidos (\u201callowlist\u201d) \u201callowableSources\u201d configurada que protege la operaci\u00f3n \u2019$import\u2019 ordinaria. Esto se ha corregido en Pathling Server 2.0.0. Como soluci\u00f3n alternativa, deshabilite la operaci\u00f3n \u2019$import-pnp\u2019 (\u201cpathling.operations.importPnpEnabled=false\u201d) o no configure las credenciales PNP."}], "lastModified": "2026-10-23T20:10:00.160", "sourceIdentifier": "security-advisories@github.com"}