Microsoft Office LTSC/LTSC 2021/LTSC 2024 Word use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Microsoft Office LTSC/LTSC 2021/LTSC 2024. This affects an unknown function of the component Word. This manipulation causes use after free. This vulnerability is handled as CVE-2026-33115. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Microsoft Office LTSC/LTSC 2021/LTSC 2024. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Word. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 04/14/2026 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2026-33115. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/15/2026).
The vulnerability scanner Nessus provides a plugin with the ID 306451 (Security Updates for Microsoft Word Products C2R (April 2026)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 16.108.26041219 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (306451). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.4
VulDB Base Score: 6.3
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.4
Vendor Vector (Microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 306451
Nessus Name: Security Updates for Microsoft Word Products C2R (April 2026)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Upgrade: Office 16.108.26041219
Timeline
04/14/2026 VulDB entry created04/14/2026 Advisory disclosed
04/14/2026 Countermeasure disclosed
04/15/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-33115 (🔒)
GCVE (CVE): GCVE-0-2026-33115
GCVE (VulDB): GCVE-100-357541
Entry
Created: 04/14/2026 20:53Updated: 04/15/2026 23:13
Changes: 04/14/2026 20:53 (33), 04/14/2026 20:57 (37), 04/15/2026 23:13 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.