CVE-2025-52968: CSRF
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-52968?
CVE-2025-52968 has not been officially assigned a severity, but it poses a risk of CSRF due to cookie handling issues.
How do I fix CVE-2025-52968?
To fix CVE-2025-52968, consider upgrading xdg-utils to a version beyond 1.2.1, if available.
What types of attacks can CVE-2025-52968 enable?
CVE-2025-52968 can potentially facilitate Cross-Site Request Forgery (CSRF) attacks.
Which versions of xdg-utils are affected by CVE-2025-52968?
CVE-2025-52968 affects xdg-utils xdg-open version 1.2.1 and earlier.
Is CVE-2025-52968 widely exploited?
As of now, there are no known active exploits for CVE-2025-52968, but the vulnerability should still be addressed.