Filtered by vendor Vtk
                         Subscriptions
                    
                    
                
                        Filtered by product Vtk
                         Subscriptions
                    
                    
                
                    Total
                    5 CVE
                
            | CVE | Vendors | Products | Updated | CVSS v3.1 | 
|---|---|---|---|---|
| CVE-2025-57107 | 1 Vtk | 1 Vtk | 2025-11-03 | 7.1 High | 
| Kitware VTK (Visualization Toolkit) through 9.5.0 contains a heap buffer overflow vulnerability in vtkGLTFDocumentLoader. When processing specially crafted GLTF files, the copy constructor of Accessor objects fails to properly validate buffer boundaries before performing memory read operations. | ||||
| CVE-2025-57108 | 1 Vtk | 1 Vtk | 2025-11-03 | 9.8 Critical | 
| Kitware VTK (Visualization Toolkit) through 9.5.0 contains a heap use-after-free vulnerability in vtkGLTFDocumentLoader. The vulnerability manifests during mesh object copy operations where vector members are accessed after the underlying memory has been freed, specifically when handling GLTF files with corrupted or invalid mesh reference structures. | ||||
| CVE-2025-57106 | 1 Vtk | 1 Vtk | 2025-11-03 | 7.5 High | 
| Kitware VTK (Visualization Toolkit) up to 9.5.0 is vulnerable to Buffer Overflow in vtkGLTFDocumentLoader. The vulnerability occurs in the BufferDataExtractionWorker template function when processing GLTF accessor data. | ||||
| CVE-2025-57109 | 1 Vtk | 1 Vtk | 2025-10-31 | 6.5 Medium | 
| Kitware VTK (Visualization Toolkit) 9.5.0 is vulnerable to Heap Use-After-Free in vtkGLTFImporter::ImportActors. When processing GLTF files with invalid scene node references, the application accesses string members of mesh objects that have been previously freed during actor import operations. | ||||
| CVE-2021-42521 | 1 Vtk | 1 Vtk | 2024-11-21 | 7.5 High | 
| There is a NULL pointer dereference vulnerability in VTK before 9.2.5, and it lies in IO/Infovis/vtkXMLTreeReader.cxx. The vendor didn't check the return value of libxml2 API 'xmlDocGetRootElement', and try to dereference it. It is unsafe as the return value can be NULL and that NULL pointer dereference may crash the application. | ||||
                            
                                
                                
                                    Page 1 of 1.