CVE-2023-26302

CLI crash via unhandled invalid UTF-8

Published Feb 22, 2023 · Updated Mar 11, 2025

Improper alternate-encoding handling in markdown-it-py before 2.2.0 allows local users to crash its CLI with an invalid UTF-8 file. The convert_file function reads Markdown through the platform-default text decoder without handling decoding errors, so an invalid byte terminates the process instead of producing output. The attacker must be able to place or select a malformed file for CLI parsing; the affected invocation crashes, while the library parser and other processes remain outside the reported impact.

CVSS severity3.3
Low
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper alternate-encoding handling in markdown-it-py before 2.2.0 allows local users to crash its CLI with an invalid UTF-8 file. The convert_file function reads Markdown through the platform-default text decoder without handling decoding errors, so an invalid byte terminates the process instead of producing output. The attacker must be able to place or select a malformed file for CLI parsing; the affected invocation crashes, while the library parser and other processes remain outside the reported impact.

The record

CVE
CVE-2023-26302
Published
Feb 22, 2023
Updated
Mar 11, 2025
Vendor
Executable Books
Product
markdown-it-py
Classifications
CWE-173, CAPEC-267
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 22, 2023CVE publishedPublication date reported by the CVE source.
  2. Mar 11, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <v2.2.0 changes=[{"at":"commit 53ca3e9","status":"unaffected"}]

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Executable Books · markdown-it-pyversion=0 <v2.2.0 changes=[{"at":"commit 53ca3e9","status":"unaffected"}]

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
7.1GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
3.3Canonical Ltd.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-173Improper Handling of Alternate Encoding
CAPEC-267Leverage Alternate Encoding

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo