CVE-2026-47662

{"id": "CVE-2026-47662", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-47662", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-13T18:36:24.137165Z"}}], "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-07T21:17:28.347", "references": [{"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-26hp-x47g-x95q", "source": "security-advisories@github.com"}, {"url": "https://github.com/aehrc/pathling/security/advisories/GHSA-26hp-x47g-x95q", "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-522"}, {"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, Pathling's typed CRUD/search/batch FHIR surface allows an authenticated caller with only coarse operation authorities to act on attacker-chosen resource families because those entrypoints do not consistently enforce the documented per-resource `read` and `write` authorities. The documented authorization model requires an operation authority (e.g. `pathling:search`) to be paired with the matching per-resource `read` or `write` authority (e.g. `pathling:read:Patient`). Delete and batch are documented to require write authority for all referenced resource types. However, typed search, update, and related handlers are annotated only with `@OperationAccess(...)` and act on the provider-selected resource type without checking the corresponding per-resource authority. This is fixed in Pathling Server 2.0.0."}, {"lang": "es", "value": "Pathling es un conjunto de herramientas que facilitan el uso de FHIR y la terminolog\u00eda cl\u00ednica dentro del an\u00e1lisis de datos de salud. Antes de la versi\u00f3n 2.0.0 de Pathling Server, la superficie FHIR tipada de CRUD/b\u00fasqueda/lote de Pathling permite a un llamador autenticado con solo autoridades de operaci\u00f3n generales actuar sobre familias de recursos elegidas por el atacante porque esos puntos de entrada no aplican consistentemente las autoridades documentadas de \u2019lectura\u2019 y \u2019escritura\u2019 por recurso. El modelo de autorizaci\u00f3n documentado requiere que una autoridad de operaci\u00f3n (p. ej., \u2019pathling:search\u2019) se empareje con la autoridad de \u2019lectura\u2019 o \u2019escritura\u2019 por recurso correspondiente (p. ej., \u2019pathling:read:Patient\u2019). Eliminar y lote est\u00e1n documentados para requerir autoridad de escritura para todos los tipos de recursos referenciados. Sin embargo, la b\u00fasqueda tipada, la actualizaci\u00f3n y los manejadores relacionados est\u00e1n anotados solo con \u2019@OperationAccess(...)\u2019 y act\u00faan sobre el tipo de recurso seleccionado por el proveedor sin verificar la autoridad por recurso correspondiente. Esto se ha corregido en Pathling Server 2.0.0."}], "lastModified": "2026-10-23T20:10:00.160", "sourceIdentifier": "security-advisories@github.com"}