PoC Monitor
← All CVEs
CVE-2025-53766published 12 Aug 2025 17:10 UTCData: JSON · API

Microsoft Office for Android

GDI+ Remote Code Execution Vulnerability

Heap-based buffer overflow in Windows GDI+ allows an unauthorized attacker to execute code over a network.

First public PoC 2.6 daysafter publication · 15 Aug 2025
Public PoCs11 on GitHub
CVSS9.8critical · scored by CNA · CWE-122
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Microsoft Microsoft Office for Android
  • >= 16.0.1, < 16.0.19127.20000

Fixed in 16.0.19127.20000

Microsoft Microsoft Office for Universal
  • >= 16.0.1, < 16.0.14326.22618

Fixed in 16.0.14326.22618

Microsoft Windows 10 Version 1507
  • >= 10.0.10240.0, < 10.0.10240.21100

Fixed in 10.0.10240.21100

Microsoft Windows 10 Version 1607
  • >= 10.0.14393.0, < 10.0.14393.8330

Fixed in 10.0.14393.8330

Microsoft Windows 10 Version 1809
  • >= 10.0.17763.0, < 10.0.17763.7678

Fixed in 10.0.17763.7678

Microsoft Windows 10 Version 21H2
  • >= 10.0.19044.0, < 10.0.19044.6216

Fixed in 10.0.19044.6216

Microsoft Windows 10 Version 22H2
  • >= 10.0.19045.0, < 10.0.19045.6216

Fixed in 10.0.19045.6216

Microsoft Windows 11 version 22H2
  • >= 10.0.22621.0, < 10.0.22621.5768

Fixed in 10.0.22621.5768

Microsoft Windows 11 version 22H3
  • >= 10.0.22631.0, < 10.0.22631.5768

Fixed in 10.0.22631.5768

Microsoft Windows 11 Version 23H2
  • >= 10.0.22631.0, < 10.0.22631.5768

Fixed in 10.0.22631.5768

Microsoft Windows 11 Version 24H2
  • >= 10.0.26100.0, < 10.0.26100.4946

Fixed in 10.0.26100.4946

Microsoft Windows Server 2008 R2 Service Pack 1
  • >= 6.1.7601.0, < 6.1.7601.27872

Fixed in 6.1.7601.27872

Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • >= 6.1.7601.0, < 6.1.7601.27872

Fixed in 6.1.7601.27872

Microsoft Windows Server 2008 Service Pack 2
  • >= 6.0.6003.0, < 6.0.6003.23471

Fixed in 6.0.6003.23471

Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • >= 6.0.6003.0, < 6.0.6003.23471

Fixed in 6.0.6003.23471

Microsoft Windows Server 2012
  • >= 6.2.9200.0, < 6.2.9200.25622

Fixed in 6.2.9200.25622

Microsoft Windows Server 2012 (Server Core installation)
  • >= 6.2.9200.0, < 6.2.9200.25622

Fixed in 6.2.9200.25622

Microsoft Windows Server 2012 R2
  • >= 6.3.9600.0, < 6.3.9600.22725

Fixed in 6.3.9600.22725

Microsoft Windows Server 2012 R2 (Server Core installation)
  • >= 6.3.9600.0, < 6.3.9600.22725

Fixed in 6.3.9600.22725

Microsoft Windows Server 2016
  • >= 10.0.14393.0, < 10.0.14393.8330

Fixed in 10.0.14393.8330

Microsoft Windows Server 2016 (Server Core installation)
  • >= 10.0.14393.0, < 10.0.14393.8330

Fixed in 10.0.14393.8330

Microsoft Windows Server 2019
  • >= 10.0.17763.0, < 10.0.17763.7678

Fixed in 10.0.17763.7678

Microsoft Windows Server 2019 (Server Core installation)
  • >= 10.0.17763.0, < 10.0.17763.7678

Fixed in 10.0.17763.7678

Microsoft Windows Server 2022
  • >= 10.0.20348.0, < 10.0.20348.4052

Fixed in 10.0.20348.4052

Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • >= 10.0.25398.0, < 10.0.25398.1791

Fixed in 10.0.25398.1791

Microsoft Windows Server 2025
  • >= 10.0.26100.0, < 10.0.26100.4946

Fixed in 10.0.26100.4946

Microsoft Windows Server 2025 (Server Core installation)
  • >= 10.0.26100.0, < 10.0.26100.4946

Fixed in 10.0.26100.4946

Mitigation

Upgrade Microsoft Office for Android to 16.0.19127.20000 or later.

Upgrade Microsoft Office for Universal to 16.0.14326.22618 or later.

Upgrade Windows 10 Version 1507 to 10.0.10240.21100 or later.

Upgrade Windows 10 Version 1607 to 10.0.14393.8330 or later.

Upgrade Windows 10 Version 1809 to 10.0.17763.7678 or later.

Upgrade Windows 10 Version 21H2 to 10.0.19044.6216 or later.

Upgrade Windows 10 Version 22H2 to 10.0.19045.6216 or later.

Upgrade Windows 11 version 22H2 to 10.0.22621.5768 or later.

Upgrade Windows 11 version 22H3 to 10.0.22631.5768 or later.

Upgrade Windows 11 Version 23H2 to 10.0.22631.5768 or later.

Upgrade Windows 11 Version 24H2 to 10.0.26100.4946 or later.

Upgrade Windows Server 2008 R2 Service Pack 1 to 6.1.7601.27872 or later.

Upgrade Windows Server 2008 R2 Service Pack 1 (Server Core installation) to 6.1.7601.27872 or later.

Upgrade Windows Server 2008 Service Pack 2 to 6.0.6003.23471 or later.

Upgrade Windows Server 2008 Service Pack 2 (Server Core installation) to 6.0.6003.23471 or later.

Upgrade Windows Server 2012 to 6.2.9200.25622 or later.

Upgrade Windows Server 2012 (Server Core installation) to 6.2.9200.25622 or later.

Upgrade Windows Server 2012 R2 to 6.3.9600.22725 or later.

Upgrade Windows Server 2012 R2 (Server Core installation) to 6.3.9600.22725 or later.

Upgrade Windows Server 2016 to 10.0.14393.8330 or later.

Upgrade Windows Server 2016 (Server Core installation) to 10.0.14393.8330 or later.

Upgrade Windows Server 2019 to 10.0.17763.7678 or later.

Upgrade Windows Server 2019 (Server Core installation) to 10.0.17763.7678 or later.

Upgrade Windows Server 2022 to 10.0.20348.4052 or later.

Upgrade Windows Server 2022, 23H2 Edition (Server Core installation) to 10.0.25398.1791 or later.

Upgrade Windows Server 2025 to 10.0.26100.4946 or later.

Upgrade Windows Server 2025 (Server Core installation) to 10.0.26100.4946 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published12 Aug 2025 · t = 0First public PoC15 Aug 2025 · t+2.6d

First public PoC 2.6 days after publication; not in CISA KEV. First PoC: rich98/cve_2025_53766 (created 15 Aug 2025, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
rich98/cve_2025_53766 15 Aug 2025 +2.6 d 0 PoC via PoC Index

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.