CVE-2025-53799VulnerabilityPublished 9 Sep 2025Updated 20 Feb 2026

CVE-2025-53799: Microsoft Office for Android · Use of Uninitialized Resource

Affects Microsoft Office for AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Microsoft Microsoft Office for Android	Affected =16.0.1	Fixed in–

AI-suggested

To mitigate CVE-2025-53799, organizations should: 1) Restrict physical access to devices running Microsoft Office for Android to trusted users only. 2) Educate users to avoid opening suspicious or untrusted Office documents that could trigger the vulnerability. 3) Monitor for official Microsoft security advisories and apply patches or updates promptly once released for the affected Office version. 4) Employ mobile device management (MDM) solutions to enforce security policies, including app version control and remote wipe capabilities in case of device loss. 5) Use endpoint protection tools on Android devices that can detect or block malicious files or behaviors targeting Office apps. 6) Limit the use of local accounts without strong authentication to reduce unauthorized local access. 7) Consider disabling or restricting features related to the Windows Imaging Component within Office apps if feasible until a patch is available. These steps go beyond generic advice by focusing on controlling local access, user behavior, and proactive patch management specific to this vulnerability.

Description

Use of uninitialized resource in Windows Imaging Component allows an unauthorized attacker to disclose information locally.

Impact

The primary impact of CVE-2025-53799 is unauthorized disclosure of sensitive information on affected Android devices running Microsoft Office version 16.0.1. This could lead to leakage of confidential business or personal data, potentially facilitating further attacks such as social engineering or identity theft. Since the vulnerability requires local access and user interaction, remote exploitation is not feasible, limiting the threat mainly to scenarios where attackers have physical access or have already compromised the device. Organizations relying on Microsoft Office for Android for document handling may face risks of data leakage if devices are lost, stolen, or infected with malware that can trigger the vulnerability. The lack of impact on integrity and availability means the vulnerability does not allow data modification or denial of service, but confidentiality breaches alone can have serious consequences, especially in regulated industries. The medium severity score indicates a moderate risk that should be addressed promptly to prevent potential data exposure.

CWE-908Use of Uninitialized Resource (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses or accesses a resource that has not been initialized.
Implementation
Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
Implementation
Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
Implementation
Avoid race conditions (CWE-362) during initialization routines.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53799 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Feb 2026, 21:17 UTC

WeaknessesCWE-908

Technical details

References

Community reviews

Related threats