Microsoft Excel 365/365 Apps/LTSC/LTSC 2024 protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.64- |
Summary
A vulnerability marked as problematic has been reported in Microsoft Excel 365/365 Apps/LTSC/LTSC 2024. Affected by this issue is some unknown functionality. This manipulation causes protection mechanism. This vulnerability is tracked as CVE-2026-45459. The attack is possible to be carried out remotely. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic was found in Microsoft Excel 365/365 Apps/LTSC/LTSC 2024. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality.
The weakness was disclosed 06/09/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is known as CVE-2026-45459. 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. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/09/2026).
Upgrading to version 16.0.10417.20137 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 3.8VulDB Meta Temp Score: 3.3
VulDB Base Score: 4.3
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 3.3
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: Protection mechanismCWE: CWE-693
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Unproven
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Upgrade: Excel 16.0.10417.20137
Timeline
06/09/2026 VulDB entry created06/09/2026 Advisory disclosed
06/09/2026 Countermeasure disclosed
06/09/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-45459 (🔒)
GCVE (CVE): GCVE-0-2026-45459
GCVE (VulDB): GCVE-100-369667
Entry
Created: 06/09/2026 19:51Updated: 06/09/2026 19:54
Changes: 06/09/2026 19:51 (36), 06/09/2026 19:54 (33)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.