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.

Published: 2025-06-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-52968 is rated Low Risk (16.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.05%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-52968

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-19 0.01% 0.05% +0.04%
2 2025-06-24 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-52968

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.0 1.4 [email protected]

Weakness enumeration for CVE-2025-52968

OS Trackers for CVE-2025-52968

vendor priority summary link
alpine low CVE-2025-52968: 1 source package rows (xdg-utils); 3 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2025-52968
debian unimportant CVE-2025-52968 unimportant priority: Debian including 1 source packages (xdg-utils), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-52968
redhat low — https://access.redhat.com/security/cve/CVE-2025-52968
suse low CVE-2025-52968 severity low: SUSE including 2 source package names (xdg-utils, xdg-utils-screensaver), 32 product×package rows across 31 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (31 product lines)): Will Not Fix 32. https://www.suse.com/security/cve/CVE-2025-52968/
ubuntu medium CVE-2025-52968 medium priority: Ubuntu including 1 source packages (xdg-utils), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): deferred 6, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2025-52968

Affected software / configurations for CVE-2025-52968

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-52968

cvelogic Threat Intelligence