CVE-2026-47661

{"id": "CVE-2026-47661", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-47661", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-11T01:12:05.773776Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.7, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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/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": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "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-07T20:16:51.423", "references": [{"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-8w85-f63v-3wh6", "source": "security-advisories@github.com"}, {"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-8w85-f63v-3wh6", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-22"}]}], "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, Pathling's `/$result` endpoint allows a caller who can obtain any valid async export job ID to supply `file` parameter values containing path traversal sequences. The handler verifies only the supplied `job` and never normalises or confines the requested `file` path to that job's `jobs/<jobId>` directory before opening it as a filesystem resource. Because async export scratch space lives under the same warehouse database root as persisted resource tables, an attacker can use their own export job to read other files from the warehouse. This is fixed in Pathling Server 2.0.0. As an interim mitigation, disable the async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capability to trusted callers."}, {"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, el endpoint \u201c/$result\u201d de Pathling permite a un llamador que puede obtener cualquier ID de trabajo de exportaci\u00f3n as\u00edncrono v\u00e1lido suministrar valores para el par\u00e1metro \u201cfile\u201d que contienen secuencias de salto de ruta. El gestor verifica solo el \u201cjob\u201d suministrado y nunca normaliza ni confina la ruta del \u201cfile\u201d solicitado al directorio \u201cjobs/[jobId]\u201d de ese trabajo antes de abrirlo como un recurso del sistema de archivos. Debido a que el espacio temporal de exportaci\u00f3n as\u00edncrona reside bajo la misma ra\u00edz de la base de datos del almac\u00e9n que las tablas de recursos persistentes, un atacante puede usar su propio trabajo de exportaci\u00f3n para leer otros archivos del almac\u00e9n. Esto se ha corregido en Pathling Server 2.0.0. Como mitigaci\u00f3n provisional, deshabilite las operaciones de exportaci\u00f3n as\u00edncrona (\u201cpathling.operations.exportEnabled\u201d, \u201cpatientExportEnabled\u201d, \u201cgroupExportEnabled\u201d, \u201cbulkSubmitEnabled\u201d) o habilite la autenticaci\u00f3n y restrinja la capacidad de exportaci\u00f3n a llamadores de confianza."}], "lastModified": "2026-10-23T20:10:00.160", "sourceIdentifier": "security-advisories@github.com"}