CVE-2026-46671: Rust OneNote File Parser: Path traversal in `Parser::parse_notebook` allows reading files outside the notebook directory

Published May 21, 2026
·
Updated

Impact A maliciously crafted .onetoc2 table-of-contents file can cause Parser::parsenotebook 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 onenoteparser to parse .onetoc2 files received from untrusted sources is affected. Users who only ever parse their own notebooks are not at meaningful risk.

Patches Fixed in onenoteparser 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.

Workarounds For users who cannot upgrade to 1.1.1:

- Only call Parser::parsenotebook on .onetoc2 files from trusted sources. - Alternatively, use Parser::parsesection / Parser::parsesectionbuffer on individual .one files, which do not perform the directory walk.

Other sources

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::parsenotebook 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 onenoteparser 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 onenoteparser 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::parsenotebook on .onetoc2 files from trusted sources. Alternatively, use Parser::parsesection / Parser::parsesectionbuffer on individual .one files, which do not perform the directory walk.

MITRE

Affected Software

2 affected componentsFixes available
rust/onenote_parser<1.1.1
1.1.1
msiemens Rust Onenote File Parser Rust<1.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/onenote_parser to a version that resolves this vulnerability.

    Fixed in 1.1.1
  2. Upgrade

    Upgrade onenote_parser to a version that resolves this vulnerability.

    Fixed in 1.1.1
  3. Compensating control

    For environments that cannot upgrade to onenote_parser 1.1.1, only call `Parser::parse_notebook` on `.onetoc2` files from trusted sources.

  4. Compensating control

    For environments that cannot upgrade to onenote_parser 1.1.1, avoid `Parser::parse_notebook` on `.onetoc2` files and instead use `Parser::parse_section` / `Parser::parse_section_buffer` on individual `.one` files (these do not perform the directory walk).

Event History

May 21, 2026
Advisory Published
via GitHub·09:32 PM
Data Sourced
via GitHub·09:32 PM
DescriptionSeverityWeaknessAffected Software
Jul 20, 2026
CVE Published
via MITRE·03:56 PM
Data Sourced
via MITRE·03:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-46671?

CVE-2026-46671 has a medium severity score of 4.4.

2

What vulnerability does CVE-2026-46671 exploit?

CVE-2026-46671 exploits a path traversal vulnerability in the rust/onenote_parser software.

3

How does CVE-2026-46671 affect system security?

CVE-2026-46671 allows a malicious `.onetoc2` file to access arbitrary files on the host filesystem.

4

What software is impacted by CVE-2026-46671?

CVE-2026-46671 affects the rust/onenote_parser software.

5

How can I mitigate CVE-2026-46671?

To mitigate CVE-2026-46671, avoid using untrusted `.onetoc2` files and ensure the software is updated to the latest version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203