VulnerabilityPublished 8 May 2026Updated 10 Sep 2026

CVE-2025-0509: Jre · Signing Checks Bypass

Affects jreSource GCVE Database

Not known to be exploited : upgrade to 8.0.441 or 1.8.0 soon.

Data as of 26 Oct 2026, 09:15 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.9% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.441, 1.8.0

Exploitation evidence

Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jre to 8.0.441 or 1.8.0.

Patches and advisories

Affected software

Product	Affected	Fixed in
Bitnamijre`pkg:bitnami/jre`Other threats	Affected <1.8.0 >=1.9.0 <8.0.441	Fixed in 1.8.0 8.0.441

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patch by upgrading Sparkle to version 2.6.4 or later. Refer to the vendor's security advisory and the linked pull request for detailed remediation steps. Since a patch is available, updating to the fixed version is the recommended action.

Description

A vulnerability in Sparkle before version 2.6.4 allows an attacker to bypass (Ed)DSA signing checks by replacing a signed update with a malicious payload. This affects certain versions of the Java Runtime Environment (JRE) as specified. A patch is available to address this issue.

Impact

Successful exploitation enables an attacker to deliver malicious updates by circumventing signature verification, potentially leading to execution of unauthorized code. This undermines the trust model of software updates and can compromise affected systems.

Summary

CVE-2025-0509 describes a security flaw in Sparkle, a software update framework, where an attacker can replace an existing signed update with a different payload, effectively bypassing Sparkle's (Ed)DSA signature verification. This allows unauthorized code to be delivered under the guise of a legitimate update. The vulnerability affects JRE versions prior to 1.8.0 and versions from 1.9.0 up to but not including 8.0.441. A fix has been released in Sparkle version 2.6.4 to correct this issue.

References

Community reviews

Loading reviews…