CVE-2025-0509 json
Signing Checks Bypass
published last yr. modified 2mo ago also BIT-java-2025-0509 , BIT-java-min-2025-0509 , BIT-jre-2025-0509 , EUVD-2025-0232 , GHSA-wc9m-r3v6-9p5h
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- swift github.com/sparkle-project/Sparkle 2.6.4
- bitnami java 1.8.0, 8.0.441
- bitnami java-min 1.8.0, 8.0.441
- bitnami jre 1.8.0, 8.0.441
- sparkle-project Sparkle 2.6.4
Is CVE-2025-0509 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.90% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-10).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 7.3 | CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 6.8 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.3 | CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| swift | github.com/sparkle-project/Sparkle | <2.6.4 |
2.6.4 |
| bitnami | java | <1.8.0 >=1.9.0, <8.0.441 |
1.8.0 8.0.441 |
| bitnami | java-min | <1.8.0 >=1.9.0, <8.0.441 |
1.8.0 8.0.441 |
| bitnami | jre | <1.8.0 >=1.9.0, <8.0.441 |
1.8.0 8.0.441 |
Affected products
- sparkle-project Sparkle
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
References
-
github.com
/sparkle-project/Sparkle/pull/2550
web, issue-tracking, patch
-
sparkle-project.org
/documentation/security-and-reliability/
patch
-
security.netapp.com
/advisory/ntap-20250124-0008/
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-0509
advisory, web
-
github.com
/sparkle-project/Sparkle
package
-
security.netapp.com
/advisory/ntap-20250124-0008
web
-
sparkle-project.org
/documentation/security-and-reliability
web
Sources
- CVE List CVE-2025-0509
- GitHub Advisory GHSA-wc9m-r3v6-9p5h
- NVD CVE-2025-0509
- OSV BIT-java-2025-0509
- OSV BIT-java-min-2025-0509
- OSV BIT-jre-2025-0509
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.