CVE-2026-118589

nschloe meshio VTK Reader _vtk_42.py memory allocation

Assigner: VulDB
Reserved: 28.10.2026 Published: 28.10.2026 Updated: 28.10.2026

A weakness has been identified in nschloe meshio up to 5.3.5. Impacted is an unknown function of the file meshio/_vtk_42.py of the component VTK Reader. Executing a manipulation of the argument DIMENSIONS can lead to uncontrolled memory allocation. The attack can be executed remotely. The project was informed of the problem early through an issue report but has not responded yet.

Metrics

CVSS Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X
CVSS Score: 6.9

Exploitability Metrics		Vulnerable System Impact Metrics		Subsequent System Impact Metrics
Attack Vector	Network	Confidentiality	None	Confidentiality	None
Attack Complexity	Low	Integrity	None	Integrity	None
Attack Requirements	None	Availability	Low	Availability	None
Privileges Required	None
User Interaction	None

CVSS 4.0

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:X/RL:X/RC:C
CVSS Score: 5.3

Attack Vector	Network	Scope	Unchanged
Attack Complexity	Low	Confidentiality Impact	None
Privileges Required	None	Integrity Impact	None
User Interaction	None	Availability Impact	Low

CVSS 3.1

CVSS Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:X/RL:X/RC:C
CVSS Score: 5.3

Attack Vector	Network	Scope	Unchanged
Attack Complexity	Low	Confidentiality Impact	None
Privileges Required	None	Integrity Impact	None
User Interaction	None	Availability Impact	Low

CVSS 3.0

CVSS Vector: AV:N/AC:L/Au:N/C:N/I:N/A:P/E:ND/RL:ND/RC:C
CVSS Score: 5

Access Vector	Network	Confidentiality Impact	None
Access Complexity	Low	Integrity Impact	None
Authentication	None	Availability Impact	Partial

CVSS 2.0

Product Status

Vendor	nschloe
Product	meshio
Versions	Version 5.3.0 is affected Version 5.3.1 is affected Version 5.3.2 is affected Version 5.3.3 is affected Version 5.3.4 is affected Version 5.3.5 is affected

Vendor

nschloe

Product

meshio

Versions

Version 5.3.0 is affected
Version 5.3.1 is affected
Version 5.3.2 is affected
Version 5.3.3 is affected
Version 5.3.4 is affected
Version 5.3.5 is affected

Credits

Mohammedix88 (VulDB User) reporter
VulDB CNA Team coordinator

References

Problem Types