OneNote CVE-2026-126526: Crafted Ink-to-Text Notebooks Trigger a Heap Overflow and Remote Code Execution — Fixed in the November Office Updates

Cyber · 2026-11-21 · By H.A

OneNote CVE-2026-126526: Crafted Ink-to-Text Notebooks Trigger a Heap Overflow and Remote Code Execution — Fixed in the November Office Updates

A heap-based buffer overflow in Microsoft OneNote (CVSS 8.8) lets a crafted notebook run code as the user when its ink is converted to text; silently fixed in the November 2026 Office updates and disclosed days later.

Overview

CVE-2026-126526 is a remote code execution flaw in Microsoft OneNote. It is a heap-based buffer overflow (CWE-122). To trigger it, an attacker sends a specially crafted OneNote file, and the victim opens it and converts its ink content to text. Microsoft rates the flaw Important with a CVSS 3.1 base score of 8.8 (High). Successful exploitation runs the attacker's code with the same permissions as the signed-in user.

The fix is not new. Microsoft says the bug was fixed in the November 2026 Office security updates, but the CVE was "inadvertently omitted" from the November release notes. The advisory was added afterwards, and the public CVE record appeared on 16 November 2026 at 23:27 Mauritius time (19:27 UTC). If your Office builds already include the November updates, you are protected. If Office updates are behind or deferred, this is one more reason to catch up.

The Vulnerability

What goes wrong

OneNote can convert handwriting and ink drawings into typed text. According to Microsoft's FAQ, the bug sits in this path: a OneNote file with malformed ink data makes OneNote write past the end of a memory buffer on the heap while it converts the ink. Heap overflows like this let an attacker overwrite nearby data in memory. With careful heap grooming, that can be turned into control of the program and code execution inside the OneNote process.

Microsoft has not published the vulnerable component or a proof of concept, and no researcher write-up has appeared. The internal details beyond "heap overflow during ink-to-text conversion" are therefore not public.

How an attack would work

Why the risk is moderate rather than critical

Two user actions are needed: opening the file and converting the ink. That is more friction than a preview-pane or zero-click bug, and it explains the "Exploitation Less Likely" rating. Code also runs only with the user's rights, so it is not SYSTEM-level unless it is chained with a privilege-escalation bug. Still, OneNote files have been used before: in early 2023, .one attachments were a popular way to deliver malware in phishing campaigns, until many mail filters started blocking them. Crafted notebooks paired with a believable lure ("convert my handwritten notes") are a realistic scenario.

Affected Products and Fixed Builds

Microsoft lists these products as affected, with the fixed build for each:

Semi-Annual Enterprise Channel builds from November 2026 are 2610 (Build 20527.20192), 2609 (Build 20430.20262) and 2608 (Build 20326.20318). Office 2019 and the standalone OneNote 2016 do not appear in Microsoft's affected list for this CVE.

Timeline

Detection

No exploitation has been seen, so there are no public IOCs. Hunt for the behaviour instead:

Recommended Actions

Analyst Assessment

CVE-2026-126526 is a quiet but useful reminder that Patch Tuesday release notes are not always complete. This fix shipped on time, and only the paperwork was late. Organisations that patch Office promptly need to do nothing more. Those that track remediation CVE-by-CVE against the published list may have missed it, so their vulnerability scanners and tickets could show a gap that is already fixed, or worse, miss one that is not. Exploitation needs two clear user actions and nothing is known to be in the wild, so we rate the practical risk as moderate. That could change quickly if a proof of concept appears, because OneNote files have a proven record as a phishing payload. Patch, turn on the child-process ASR rule, and move on.

Sources

REEF SENTINEL