Is there a patch available for EUVD-2026-23147?

Yes, a patch is available for EUVD-2026-23147. Update the affected software to the latest version immediately.

Mupdf EUVD-2026-23147

Q: What is the CVSS score of EUVD-2026-23147?

EUVD-2026-23147 has a CVSS 4.0 base score of 4.8 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

| CVE-2026-40505 MEDIUM

Improper Neutralization of Escape, Meta, or Control Sequences (CWE-150)

2026-04-16 VulnCheck

GHSA-hj44-m5xv-x75q

RCE Mupdf

4.8

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

4.8 MEDIUM

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

SUSE

3.3 LOW

AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Severity Changed

Apr 16, 2026 - 02:34 NVD

LOW MEDIUM

CVSS changed

Apr 16, 2026 - 02:34 NVD

3.3 (LOW) 4.8 (MEDIUM)

Analysis Generated

Apr 16, 2026 - 01:49 vuln.today

EUVD ID Assigned

Apr 16, 2026 - 01:45 euvd

EUVD-2026-23147

Analysis Generated

Apr 16, 2026 - 01:45 vuln.today

Patch released

Apr 16, 2026 - 01:45 nvd

Patch available

CVE Published

Apr 16, 2026 - 01:20 nvd

MEDIUM 4.8

DescriptionCVE.org

MuPDF mutool does not sanitize PDF metadata fields before writing them to terminal output, allowing attackers to inject arbitrary ANSI escape sequences through crafted PDF metadata. Attackers can embed malicious ANSI escape codes in PDF metadata that are passed unsanitized to the terminal when running mutool info, enabling them to clear the terminal display and render arbitrary text for social engineering attacks such as presenting fake prompts or spoofed commands.

AnalysisAI

MuPDF mutool fails to sanitize PDF metadata before displaying it in terminal output, allowing local attackers to inject ANSI escape sequences through crafted PDF files. When a user runs mutool info on a malicious PDF, embedded escape codes can clear the terminal and display fabricated text for social engineering attacks such as fake login prompts or spoofed shell commands. This is a low-severity local vulnerability (CVSS 3.3) requiring user interaction, with a vendor-released patch available.

Technical ContextAI

MuPDF is a lightweight PDF rendering library and the mutool command-line utility is used to inspect and manipulate PDF files. The vulnerability exploits insufficient input validation of PDF metadata fields (such as Title, Author, Subject) that are passed directly to terminal output without ANSI escape sequence filtering. CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences) describes the root cause: untrusted metadata content is written to the terminal without stripping control characters that the terminal interprets as commands (e.g., cursor movement, text color, display clearing). The affected product is MuPDF across versions prior to the patched commit, as indicated by the CPE string cpe:2.3:a:artifex_software_inc.:mupdf:*:*:*:*:*:*:*:* covering all versions.

RemediationAI

Update MuPDF to a version incorporating commit 0f17d789fe8c29b41e47663be82514aaca3a4dfb or later. The patch is available from the Ghostscript MuPDF repository at https://cgit.ghostscript.com/cgi-bin/cgit.cgi/mupdf.git/commit/?id=0f17d789fe8c29b41e47663be82514aaca3a4dfb. Until patched, users can mitigate by: redirecting mutool info output through a tool that sanitizes ANSI sequences (e.g., piping through sed or using the cat -v flag to display escape sequences literally), restricting mutool usage to trusted PDFs only, or disabling shell features that process PDF metadata (such as running mutool in a restricted terminal environment). As a compensating control, administrators can disable or remove mutool from systems where it is not actively required, or restrict its use to trusted internal documents only. However, these workarounds do not eliminate the social engineering vector and should be considered temporary until patching is completed.