CVE-2025-52968

xdg-open in xdg-utils through 1.2.1 can send requests containing SameSite=Strict cookies, which can facilitate CSRF. (For example, xdg-open could be modified to, by default, associate x-scheme-handler/https with the execution of a browser with command-line options that arrange for an empty cookie store, although this would add substantial complexity, and would not be considered a desirable or expected behavior by all users.) NOTE: this is disputed because integrations of xdg-open typically do not provide information about whether the xdg-open command and arguments were manually entered by a user, or whether they were the result of a navigation from content in an untrusted origin.

xdg-open in xdg-utils through 1.2.1 can send requests containing SameSite=Strict cookies, which can facilitate CSRF. (For example, xdg-open could be modified to, by default, associate x-scheme-handler/https with the execution of a browser with command-line options that arrange for an empty cookie store, although this would add substantial complexity, and would not be considered a desirable or expected behavior by all users.) NOTE: this is disputed because integrations of xdg-open typically do not provide information about whether the xdg-open command and arguments were manually entered by a user, or whether they were the result of a navigation from content in an untrusted origin.

xdg-open en xdg-utils hasta la versión 1.2.1 puede enviar solicitudes que contienen cookies SameSite=Strict, lo que facilita el CSRF. (Por ejemplo, xdg-open podría modificarse para asociar, por defecto, x-scheme-handler/https con la ejecución de un navegador con opciones de línea de comandos que gestionen un almacén de cookies vacío, aunque esto añadiría una complejidad considerable y no sería considerado un comportamiento deseable ni esperado por todos los usuarios). NOTA: Esto es controvertido porque las integraciones de xdg-open no suelen proporcionar información sobre si el comando y los argumentos de xdg-open fueron introducidos manualmente por un usuario o si fueron el resultado de una navegación desde contenido de un origen no confiable.