SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-46671

MEDIUM · CVSS 4.4 EPSS 0.14% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-20 · Last synced 2026-08-19

CyberRota Analysis

AI-Generated

The vulnerability affects the Rust OneNote File Parser used in Microsoft OneNote, allowing a maliciously crafted `.onetoc2` file to trigger the parser to access arbitrary files on the host filesystem. This could lead to file-existence probing and potential denial-of-service attacks, although direct content exfiltration is not feasible. Organizations and users who utilize the parser with untrusted `.onetoc2` files should prioritize upgrading to version 1.1.1 or implement strict controls on file sources to mitigate risk.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-46671
Severity
MEDIUM
CVSS
4.4
EPSS
0.14%
Microsoft

Original NVD Description

Rust OneNote File Parser is a parser for Microsoft OneNote files implemented in Rust. Prior to version 1.1.1, a maliciously crafted `.onetoc2` table-of-contents file can cause `Parser::parse_notebook` to open arbitrary files on the host filesystem outside the notebook's directory. The parser reads entry names listed inside the `.onetoc2` and joins them against the notebook's base directory without validating that they are relative paths confined to that directory. The parser will bail out when the target file fails to parse as a OneNote section, so direct content exfiltration through the parser's return value is not practical, though file-existence probing and denial-of-service via large or special files remain possible. Anyone using `onenote_parser` to parse .onetoc2 files received from untrusted sources is affected. Users who only ever parse their own notebooks are not at meaningful risk. The issue is fixed in onenote_parser 1.1.1. The fix rejects absolute paths, parent-directory components, and other invalid path characters in entry names, and additionally canonicalises the resolved path to confirm it stays inside the notebook's base directory. For users who cannot upgrade to 1.1.1, only call `Parser::parse_notebook` on `.onetoc2` files from trusted sources. Alternatively, use `Parser::parse_section` / `Parser::parse_section_buffer` on individual .one files, which do not perform the directory walk.

Related CVEs

Other vulnerabilities affecting the same vendor(s)