CVE-2025-8835: JasPer · NULL Pointer Dereference
Affects JasPerSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2025
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JasPer | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize patching affected JasPer library versions (4.2.0 through 4.2.5) by applying the official patch identified by commit bb7d62bd0a2a8e0e1fdb4d603f3305f955158c52. Beyond patching, organizations should implement strict access controls to limit local access to systems running vulnerable software, reducing the risk of exploitation by unauthorized users. Employing application whitelisting and monitoring for abnormal application crashes or behavior related to image processing components can help detect exploitation attempts. Additionally, organizations should audit their software dependencies to identify where JasPer is used, including indirect dependencies in third-party applications, and ensure those applications are updated or mitigated accordingly. Regular vulnerability scanning and integration of JasPer version checks into software composition analysis tools will help maintain visibility. For environments with high security requirements, consider isolating image processing workloads or running them in sandboxed containers to limit the impact of potential crashes. Finally, user training to recognize and report unusual system behavior can aid early detection of exploitation attempts.
Description
A vulnerability was found in JasPer up to 4.2.5. Affected by this vulnerability is the function jas_image_chclrspc of the file src/libjasper/base/jas_image.c of the component Image Color Space Conversion Handler. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The identifier of the patch is bb7d62bd0a2a8e0e1fdb4d603f3305f955158c52. It is recommended to apply a patch to fix this issue.
References
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- vuldb.com (opens in a new tab)
- github.com/jasper-software/jasper/issues/400 (opens in a new tab)
- github.com/jasper-software/jasper/issues/400 (opens in a new tab)
- drive.google.com/file/d/1E754R-FsFkNJp9OYtu6Dqjv47uGSVP18/view?usp=sharing (opens in a new tab)
- github.com/jasper-software/jasper/commit/bb7d62bd0a2a8e0e1fdb4d603f3305f955158c52 (opens in a new tab)