Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46671 medium CVSS 4.4

Path Traversal in onenote_parser (CVE-2026-46671)

Summary

Path traversal in onenote_parser (CVE-2026-46671). Risk of unauthorized operations or information disclosure. Exploitable via onenote_parser. Mitigation: upgrade to 1.1.1 or later.

Original description

The description as published by the source.

Impact

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.

Patches

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.

Workarounds

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-46671 has been found in onenote_parser.
Attackers can target a specific entry point like onenote_parser over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade onenote_parser to 1.1.1 or later.
If unsure, ask your IT team or search "onenote_parser CVE-2026-46671" on the vendor's site.

CVE-2026-46671 (onenote_parser) — CWE-22 / CVSS v3 4.4
Attack vector: local / unauthenticated
Attack surface: onenote_parser
Patched: 1.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in onenote_parser. Attackers reach the vulnerable code path via onenote_parser without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of onenote_parser. Attack surface: onenote_parser.

🔥 Severity

Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'onenote_parser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'onenote_parser' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で onenote_parser を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade onenote_parser to 1.1.1

    ステージング環境で 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust onenote_parser
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1"}]}]
crates.io onenote_parser
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details