Expired Pointer Dereference Affecting vtk package, versions [0,]
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-VTK-22113923
- published1 Nov 2026
- disclosed29 Oct 2026
- creditEmmanuel Tacheau
Introduced: 29 Oct 2026
NewCVE-2026-42057 (opens in a new tab)How to fix?
There is no fixed version for vtk.
Overview
Affected versions of this package are vulnerable to Expired Pointer Dereference in the vtkPNGReader::vtkInternals::HandleLibPngError method in IO/Image/vtkPNGReader.cxx. An attacker can crash a VTK application with a malformed PNG that passes png_read_info header parsing but fails during png_read_image or png_read_end, because libpng then executes a longjmp back to a setjmp that HandleLibPngError established before returning, and the following fclose(fp) runs against a stale fp from the unwound frame. Exploitation requires the application to decode an untrusted PNG through the VTK PNG reader, and on glibc 2.24+ the _IO_vtable_check hardening can turn some cases into a SIGABRT, a mitigation that may be absent on other C libraries.