# CVE-2024-40446: An issue in forkosh Mime Tex before v.1.77 allows an attacker to execute arbitrary code via a crafted script


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Apr 2025
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2024-40446, GHSA-rw43-mgp5-rf2m, UBUNTU-CVE-2024-40446

## What is CVE-2024-40446?

CVE-2024-40446 is a critical vulnerability in n/a, published on 22 Apr 2025. 

### Official description

An issue in forkosh Mime Tex before v.1.77 allows an attacker to execute arbitrary code via a crafted script

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-40446?

It affects 1 product.


Products: Ctan Mimetex.

## How do I fix CVE-2024-40446?

Upgrade to a fixed version.

## Is CVE-2024-40446 being exploited?

There is no known exploitation of CVE-2024-40446 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-40445](https://insights.sbomify.com/CVE-2024-40445/): Path traversal in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40446 and fix it if it is affected.

What it is: CVE-2024-40446 is a critical vulnerability in n/a, published on 22 Apr 2025. 
Exploitation: There is no known exploitation of CVE-2024-40446 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-40446/ (Markdown: https://insights.sbomify.com/CVE-2024-40446/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-40446
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-40446
- OSV: https://osv.dev/vulnerability/CVE-2024-40446

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-40446/
Summaries are generated and may contain mistakes; the official description above is the record.