Cyber Resilience

CVE-2025-30379

Microsoft Office Long Term Servicing Channel 2021 … 2024

Published
13 May 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0050 40th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2025-30379 is a high-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Microsoft Office Long Term Servicing Channel. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Release of invalid pointer or reference in Microsoft Office Excel allows an unauthorized attacker to execute code locally.

CWE(s)
CWE-763

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-24953Same product: Microsoft 365 Apps
CVE-2024-43465Same product: Microsoft 365 Apps
CVE-2024-30042Same product: Microsoft 365 Apps
CVE-2023-32029Same product: Microsoft 365 Apps
CVE-2023-36766Same product: Microsoft 365 Apps
CVE-2023-35371Same product: Microsoft 365 Apps
CVE-2023-36896Same product: Microsoft 365 Apps
CVE-2023-36041Same product: Microsoft 365 Apps
CVE-2023-33133Same product: Microsoft 365 Apps
CVE-2024-49027Same product: Microsoft 365 Apps

Affected Assets

microsoft
365 apps
all versions
microsoft
excel
2016
microsoft
office
2019
microsoft
office long term servicing channel
2021, 2024
microsoft
office online server
≤ 16.0.10417.20010

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly exercises deallocation paths and can find incorrect release calls or mismatched alloc/free pairs.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can mandate safe memory-management idioms and static checks that avoid invalid releases.

SA-3 System Development Life Cycle partial match

An SDLC that incorporates security can embed memory-safety requirements, reducing the chance such coding errors are introduced.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles require correct resource management and memory-release patterns that stop invalid pointer releases from being coded.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent invalid pointer release errors during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect invalid pointer releases before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices can mandate proper memory-management APIs and reviews that catch incorrect deallocation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct use of release functions and pointer validation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include safe memory handling and resource-lifetime rules.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.

References