CVE-2026-78386

{"id": "CVE-2026-78386", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-78386", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-24T15:10:10.690433Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "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": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "affectedData": [{"repo": "https://github.com/RansomLook/RansomLook/", "vendor": "ransomlook", "product": "ransomlook", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "2.0.0"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-24T14:17:06.090", "references": [{"url": "https://github.com/RansomLook/RansomLook/commit/cc9182930306ff36c7b3424817d49f18df3c85d1", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "description": [{"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "RansomLook exposed sensitive operator-side scraping configuration through multiple unauthenticated API responses. Location records associated with ransomware groups and markets were returned largely verbatim to unauthenticated callers whenever the location itself was not marked as private.\n\n\nThese records could contain internal fields such as header, which may include authentication headers, session cookies, or other credentials used to access monitored websites; init_script, which may contain logic used to bypass CAPTCHA, anti-bot protections, or paywalls; and browser, which discloses details about the scraping environment.\n\n\nAn unauthenticated remote attacker could query the affected API endpoints and obtain these values. Leaked authentication material could potentially be replayed against the monitored service, while disclosure of scraping and bypass logic could allow site operators or other attackers to identify and defeat RansomLook's collection mechanisms.\n\n\nThe patch introduces an explicit allowlist of fields permitted in public location records and strips all operator-side fields before returning data to unauthenticated users.\n\n\nThe accompanying change from <string:postname> to <path:postname> appears to be a functional correction allowing legitimate post titles containing / and does not, based on this patch alone, represent the security issue."}, {"lang": "es", "value": "RansomLook expuso la configuraci\u00f3n de scraping sensible del lado del operador a trav\u00e9s de m\u00faltiples respuestas de API no autenticadas. Los registros de ubicaci\u00f3n asociados con grupos y mercados de ransomware fueron devueltos en gran parte textualmente a los llamadores no autenticados siempre que la ubicaci\u00f3n misma no estuviera marcada como privada.\n\nEstos registros podr\u00edan contener campos internos como header, que pueden incluir encabezados de autenticaci\u00f3n, cookies de sesi\u00f3n u otras credenciales utilizadas para acceder a sitios web monitoreados; init_script, que puede contener l\u00f3gica utilizada para eludir CAPTCHA, protecciones anti-bot o muros de pago; y browser, que revela detalles sobre el entorno de scraping.\n\nUn atacante remoto no autenticado podr\u00eda consultar los puntos finales de API afectados y obtener estos valores. El material de autenticaci\u00f3n filtrado podr\u00eda ser potencialmente reproducido contra el servicio monitoreado, mientras que la divulgaci\u00f3n de la l\u00f3gica de scraping y elusi\u00f3n podr\u00eda permitir a los operadores del sitio u otros atacantes identificar y derrotar los mecanismos de recolecci\u00f3n de RansomLook.\n\nEl parche introduce una lista de permitidos expl\u00edcita de campos permitidos en los registros de ubicaci\u00f3n p\u00fablicos y elimina todos los campos del lado del operador antes de devolver datos a usuarios no autenticados.\n\nEl cambio que lo acompa\u00f1a de <string:postname> a <path:postname> parece ser una correcci\u00f3n funcional que permite t\u00edtulos de publicaciones leg\u00edtimos que contienen / y no, bas\u00e1ndose solo en este parche, representa el problema de seguridad."}], "lastModified": "2026-10-14T13:10:00.187", "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}