Vulnerabilities
All
My stack
Known exploited
Public exploit
Critical (9+)
Likely exploited (EPSS ≥ 50%)
Changed, 24 h
New, 24 h
Sort:
risk
modified
published
CVSS
EPSS
| CVE | CVSS | EPSS | Vendor, product | Description | Modified |
|---|---|---|---|---|---|
| CVE-2017-8509 | 8.8 high | 18.0% | microsoft, office, office_compatibility_pack, office_web_apps | A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506. | 15 Oct |
| CVE-2026-97781 | 8.8 high | 1.0% | microsoft, 365_apps | Improper neutralization of special elements used in a command ('command injection') in Microsoft Office OneNote allows an unauthorized attacker to execute code over a network. | 16 Oct |
| CVE-2026-102858 | 8.8 high | 1.0% | microsoft, microsoft_365, office_2021, office_2024 | Heap-based buffer overflow in Microsoft Office OneNote allows an unauthorized attacker to execute code over a network. | 15 Oct |
| CVE-2026-55133 | 7.8 high | 0.00% | microsoft, microsoft 365 apps for enterprise, microsoft office 365 for mac, microsoft office ltsc for mac 2021 | Heap-based buffer overflow in Microsoft Office OneNote allows an unauthorized attacker to execute code locally. | 24 h ago |
| CVE-2026-96997 | 7.8 high | 0.00% | microsoft, 365_apps, microsoft_365, office_2021 | Use after free in Microsoft Office OneNote allows an authorized attacker to elevate privileges locally. | 15 Oct |
| CVE-2026-46671 | 4.4 medium | 0.00% | msiemens, rust_onenote_file_parser | 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. | Sat 24 Oct |
6 of 6
Download these 6 as CSV · subscribe to this list.
EPSS scores: 2026-10-28. NVD cursor: 2026-10-29 00:22. The News page shows only notable CVEs (KEV, your stack, new criticals, EPSS over 50%, or active exploitation per SSVC); this table has all of them.