# CVE-2023-32668: Server-side request forgery in n/a

> Attackers can force LuaTeX to make arbitrary network requests via malicious documents due to unrestricted socket library access by default.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 May 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-32668, GHSA-hm67-jh95-48xh, OESA-2025-2694, UBUNTU-CVE-2023-32668

## What is CVE-2023-32668?

CVE-2023-32668 is a medium-severity server-side request forgery vulnerability in n/a, published on 11 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

LuaTeX before 1.17.0 allows a document (compiled with the default settings) to make arbitrary network requests. This occurs because full access to the socket library is permitted by default, as stated in the documentation. This also affects TeX Live before 2023 r66984 and MiKTeX before 23.5.

## Which versions are affected by CVE-2023-32668?

It affects 3 products.


Products: Luatex Project Luatex, Miktex Miktex, Tug Tex Live.

## How do I fix CVE-2023-32668?

Upgrade to a fixed version.

## Is CVE-2023-32668 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-32700](https://insights.sbomify.com/CVE-2023-32700/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32668 and fix it if it is affected.

What it is: CVE-2023-32668 is a medium-severity server-side request forgery vulnerability in n/a, published on 11 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-32668 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-2023-32668/ (Markdown: https://insights.sbomify.com/CVE-2023-32668/index.md)
```

## Sources

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

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