Libigl is a geometry-processing library embedded in 3D modeling, visualization, and computational geometry applications across research and professional software. Its vulnerability profile concentrates in a single library product and recurs through memory-safety weakness classes—out-of-bounds writes and reads, stack- and heap-based buffer overflows, and improper array-index validation—that are typical of native C++ codebases handling unvalidated geometric or mesh data. Defenders should track this library's releases particularly where it appears in applications ingesting untrusted geometric models or point clouds; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libigl over time
Signals from CVEs in this vendor scope (17 CVEs).
17 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-23951HIGH Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds write. An a | May 28, 2024 | 8.8 | 26 | NO | NO |
CVE-2024-23949HIGH Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds write. An a | May 28, 2024 | 8.8 | 26 | NO | NO |
CVE-2024-23948HIGH Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds write. An a | May 28, 2024 | 8.8 | 26 | NO | NO |
CVE-2024-23947HIGH Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds write. An a | May 28, 2024 | 8.8 | 26 | NO | NO |
CVE-2023-35953HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0. A specially-crafted .off file can lead to a buffer overflow. An attack | May 28, 2024 | 7.8 | 24 | NO | NO |
CVE-2023-35952HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0. A specially-crafted .off file can lead to a buffer overflow. An attack | May 28, 2024 | 7.8 | 24 | NO | NO |
CVE-2023-35951HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0. A specially-crafted .off file can lead to a buffer overflow. An attack | May 28, 2024 | 7.8 | 24 | NO | NO |
CVE-2024-24686HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An | May 28, 2024 | 7.8 | 23 | NO | NO |
CVE-2024-24685HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An | May 28, 2024 | 7.8 | 23 | NO | NO |
CVE-2024-24684HIGH Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An | May 28, 2024 | 7.8 | 23 | NO | NO |
Signals from CVEs in this vendor scope (17 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libigl.
Media articles that mention a CVE ID that affects a product developed by Libigl — matched by CVE ID, not by vendor name.