Remote code execution via heap buffer overflow
Published Aug 12, 2025 · Updated Feb 13, 2026
Heap-based buffer overflow in Microsoft Teams clients allows remote attackers to execute code after user interaction. Microsoft has not disclosed the affected component, the input that reaches it, or the operation that writes beyond the heap allocation. Exploitation requires no prior authentication but requires a user to interact with attacker-supplied network content, after which code runs in the Teams client's security context.
Summary
What happened
Heap-based buffer overflow in Microsoft Teams clients allows remote attackers to execute code after user interaction. Microsoft has not disclosed the affected component, the input that reaches it, or the operation that writes beyond the heap allocation. Exploitation requires no prior authentication but requires a user to interact with attacker-supplied network content, after which code runs in the Teams client's security context.
The record
- CVE
- CVE-2025-53783
- Published
- Aug 12, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Microsoft Teams
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0.0 <25122.1207.3700.1444
- Affected versionversion=1.0.0 <25122.1415.3698.6812
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo