Description
Heap-based buffer overflow in Microsoft Office allows an unauthorized attacker to execute code locally.
Basic information
- Type
- unreviewed
- Severity
- high
- Advisory on GitHub
- Open advisory ↗
- Repository advisory
- —
- Source code
- Not specified
- Published (advisory)
- 2026-06-09 18:30:49 UTC
- Updated
- 2026-06-17 21:34:33 UTC
- NVD published
- 2026-06-09
EPSS Score
| Score |
Percentile |
|
0.28%
|
19.87% |
CVSS Scores
| Base score |
Version |
Severity |
Vector |
|
8.4
|
3.1 |
—
|
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
- Attack vector (AV:L)
- They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:N)
- No account or special rights needed—anonymous or random user is enough.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:H)
- Serious risk that confidential data gets exposed in a big way.
- Integrity (I:H)
- They could widely tamper with or forge data—trust in the data is badly hurt.
- Availability (A:H)
- Could take the service down hard or make it unusable for people who depend on it.
|
cvelogic
Threat Intelligence