Skip to main content
No exploitation reported

CVE-2024-23951

No exploitation reported by the sources we read.

  • Published2024-05-28
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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 attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the `igl::MshLoader::parse_element_field` function while handling an `ascii`.msh` file.

Timeline

dates in UTC
  1. 2024-05-2814:15CVE publishedNVD

Versions per branch

NVD · CISA-ADP
Libigl
BranchAffectedFixed in
2.5= 2.5.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As talos, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • libigl
    Affected
    • = v2.5.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-05-28

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • slic3r-prusaUbuntu:26.10all versions · no fixed version listed
  • slic3r-prusaUbuntu:26.04:LTSall versions · no fixed version listed
  • slic3r-prusaUbuntu:25.10all versions · no fixed version listed
  • slic3r-prusaUbuntu:24.04:LTSall versions · no fixed version listed
  • slic3r-prusaUbuntu:22.04:LTSall versions · no fixed version listed
  • slic3r-prusaUbuntu:20.04:LTSall versions · no fixed version listed
  • slic3r-prusaUbuntu:18.04:LTSall versions · no fixed version listed

Vendor advisories

  • CVE-2024-23951 Red Hat Product Security

    meshlab: specially crafted .msh file can lead to an out-of-bounds write

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2024-07-22
  • CNACVSS 3.18.8known since 2026-10-23
  • CNAweakness (CWE)CWE-787known since 2026-10-23
  • FIRST EPSSEPSS score0.9 %2026-11-08
  • OSVaffected packages—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2024-05-28
Last Modified
2026-06-17
NVD status
Analyzed

Frequently asked questions

What is CVE-2024-23951?

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 attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the `igl::MshLoader::parse_element_field` function while handling an `ascii`.msh` file.

Is CVE-2024-23951 actively exploited?

Active exploitation of CVE-2024-23951 has not been confirmed. Its EPSS score was 0.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-23951?

CVE-2024-23951 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running meshlab? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record