Skip to main content
VulnerabilityPublished Updated

CVE-2023-51885: Mathtex v · Buffer Overflow

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmmathtexpkg:npm/mathtexOther threatsAffected
  • >=1.0 <=1.05
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches, European organizations should first identify all instances of Mathtex version 1.05 or earlier within their environments, including embedded uses in third-party applications. Immediate mitigation steps include: 1) Restricting network access to services that process LaTeX strings using Mathtex, employing network segmentation and firewall rules to limit exposure. 2) Implementing input validation and sanitization at the application layer to detect and block abnormally long or malformed LaTeX strings before they reach the vulnerable component. 3) Employing runtime protections such as Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), and stack canaries to reduce the likelihood of successful exploitation. 4) Monitoring logs and network traffic for anomalous activities indicative of exploitation attempts, such as unusually long LaTeX inputs or unexpected process behaviors. 5) Engaging with software vendors or open-source communities to track the release of patches or updated versions of Mathtex and planning prompt deployment once available. 6) Considering temporary removal or replacement of Mathtex-dependent functionality if feasible until a secure version is deployed. These targeted mitigations go beyond generic advice by focusing on the specific attack vector and the operational context of Mathtex usage.

Description

Buffer Overflow vulnerability in Mathtex v.1.05 and before allows a remote attacker to execute arbitrary code via the length of the LaTeX string component.

References

Community reviews

Loading reviews…