CVE-2025-0509 | Signing Checks Bypass

A security issue was found in Sparkle before version 2.6.4. An attacker can replace an existing signed update with another payload, bypassing Sparkle’s (Ed)DSA signing checks.

Published: 2025-02-04 Last update: 2025-08-05 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-0509 is rated Low Risk (34.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-0509

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 2025-11-21 0.20% 0.05% -0.15%
2 2025-11-18 0.03% 0.20% +0.17%
3 2025-03-30 0.03%

Full EPSS history (5 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.7 6.0 [email protected]
6.8 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.9 5.9 [email protected]

Weakness enumeration for CVE-2025-0509

GitHub Security Advisory for CVE-2025-0509

OS Trackers for CVE-2025-0509

vendor priority summary link
debian unimportant CVE-2025-0509 unimportant priority: Debian including 1 source packages (openjdk-8), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-0509
ubuntu medium CVE-2025-0509 medium priority: Ubuntu including 11 source packages (openjdk-13, openjdk-16, …), 60 status rows across 7 suites (bionic, focal, jammy, noble, oracular, upstream, xenial): not-affected 33, DNE 23, ignored 4. https://ubuntu.com/security/CVE-2025-0509

Affected software / configurations for CVE-2025-0509

Vendor Product Version Raw CPE
sparkle-project sparkle < 2.6.4 cpe:2.3:a:sparkle-project:sparkle:*:*:*:*:*:*:*:*
netapp hci_compute_node cpe:2.3:o:netapp:hci_compute_node:-:*:*:*:*:*:*:*
netapp oncommand_workflow_automation cpe:2.3:a:netapp:oncommand_workflow_automation:-:*:*:*:*:*:*:*

References for CVE-2025-0509

cvelogic Threat Intelligence