CVE-2026-24807: liuyueyi quick-media · Improper Verification of Cryptographic Signature
Affects liuyueyi quick-mediaSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to v1.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in v1.0, 1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/S:N/AU:Y/R:U/V:C/RE:M/U:AmberExploitation evidence
Disclosed: evidence found.
CVE published 27 Jan 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.
What to do
Upgrade quick-media to v1.0; liuyueyi/quick-media and quick-media to 1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| liuyueyiquick-media | Affected
| Fixed in
|
GitHubliuyueyi/quick-mediapkg:github/liuyueyi/quick-mediaOther threats | Affected
| Fixed in
|
GitHubquick-mediapkg:github/quick-mediaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, cautious use of the affected components is advised, especially in security-critical contexts.
Description
Improper Verification of Cryptographic Signature vulnerability in liuyueyi quick-media (plugins/svg-plugin/batik-codec-fix/src/main/java/org/apache/batik/ext/awt/image/codec/util modules). This vulnerability is associated with program files SeekableOutputStream.Java. This issue affects quick-media: before v1.0.