CVE-2026-69078

{"id": "CVE-2026-69078", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-69078", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-03T10:55:56.325226Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.8, "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:L/VA:N/SC:L/SI:L/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": "LOW", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "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/MISP/cti-transmute/", "vendor": "misp", "product": "cti-transmute", "versions": [{"status": "affected", "version": "0", "versionType": "semver", "lessThanOrEqual": "1.4.0"}], "defaultStatus": "unaffected"}]}], "published": "2026-08-03T10:16:33.243", "references": [{"url": "https://github.com/MISP/cti-transmute/commit/20f35307bcb706c8dd8ca3884a88fb36b05b5244", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8", "description": [{"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "CTI-Transmute is affected by a server-side request forgery vulnerability in the evaluation report PDF-generation functionality.\n\nUser-controlled CTI content, including conversion names, descriptions, and comments, is converted from Markdown to HTML and rendered as a PDF using WeasyPrint. Before the patch, the renderer used WeasyPrint\u2019s default URL-fetching behavior without restricting the protocols or destinations that could be referenced by the generated HTML.\n\nAn attacker able to supply content included in an evaluation report could inject crafted resource references using schemes such as http://, https://, or file://. When the report was rendered, CTI-Transmute could fetch these resources using the application server\u2019s network connectivity and filesystem privileges.\n\nSuccessful exploitation could allow an attacker to:\n\n * access services available only from the CTI-Transmute server or its internal network;\n * probe internal hosts and service endpoints;\n * retrieve local files readable by the application process; and\n * expose fetched content through the generated PDF, depending on the referenced resource type and rendering context.\n\n\nThe vulnerability is corrected by providing WeasyPrint with a restrictive URL fetcher that permits only self-contained data: URIs. The externally hosted Google Fonts stylesheet was also removed so that PDF generation performs no intentional network or filesystem fetches."}, {"lang": "es", "value": "CTI-Transmute se ve afectado por una vulnerabilidad de falsificaci\u00f3n de petici\u00f3n del lado del servidor en la funcionalidad de generaci\u00f3n de PDF de informes de evaluaci\u00f3n.\n\nEl contenido CTI controlado por el usuario, incluyendo nombres de conversi\u00f3n, descripciones y comentarios, se convierte de Markdown a HTML y se renderiza como un PDF usando WeasyPrint. Antes del parche, el renderizador utilizaba el comportamiento predeterminado de WeasyPrint para la obtenci\u00f3n de URL sin restringir los protocolos o destinos que pod\u00edan ser referenciados por el HTML generado.\n\nUn atacante capaz de proporcionar contenido incluido en un informe de evaluaci\u00f3n podr\u00eda inyectar referencias de recursos manipuladas utilizando esquemas como http://, https://, o file: //. Cuando se renderizaba el informe, CTI-Transmute podr\u00eda obtener estos recursos utilizando la conectividad de red del servidor de aplicaciones y los privilegios del sistema de archivos.\n\nLa explotaci\u00f3n exitosa podr\u00eda permitir a un atacante:\n\n * acceder a servicios disponibles solo desde el servidor CTI-Transmute o su red interna;\n * sondear hosts internos y puntos finales de servicio;\n * recuperar archivos locales legibles por el proceso de la aplicaci\u00f3n; y\n * exponer el contenido obtenido a trav\u00e9s del PDF generado, dependiendo del tipo de recurso referenciado y el contexto de renderizado.\n\nLa vulnerabilidad se corrige proporcionando a WeasyPrint un recuperador de URL restrictivo que permite solo URIs de datos autocontenidos. La hoja de estilo de Google Fonts alojada externamente tambi\u00e9n fue eliminada para que la generaci\u00f3n de PDF no realice recuperaciones intencionales de red o sistema de archivos."}], "lastModified": "2026-10-23T22:10:00.160", "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8"}