What is CWE-122?
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CWE-122 is a variant-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of High. Applicable platforms: Language: Memory-Unsafe; Language: C; Language: C++; Technology: Not Technology-Specific.
Source: MITRE CWE (CWE-122 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- Availability — DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory). Buffer overflows generally lead to crashes. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
- Integrity, Confidentiality, Availability, Access Control — Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Modify Memory. Buffer overflows often can be used to execute arbitrary code, which is usually outside the scope of a program's implicit security policy. Besides important user data, heap-based overflows can be used to overwrite function pointers that may be living in memory, pointing it to the attacker's code. Even in applications that do not explicitly use function pointers, the run-time will usually leave many in memory. For example, object methods in C++ are generally implemented using function pointers…
- Integrity, Confidentiality, Availability, Access Control, Other — Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Other. When the consequence is arbitrary code execution, this can often be used to subvert any other security service.
Source: MITRE CWE, common consequences.
How CWE-122 is exploited in the wild
Threadlinqs maps 252 CVEs to CWE-122, published between 2009-10-13 and 2026-11-17. 9 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 3 are tied to ransomware campaigns. By CVSS v3 severity the set splits into 47 critical, 180 high, 15 medium, 1 low. The highest EPSS score in the set is 86.5% (CVE-2009-3459), the modelled probability of exploitation in the next 30 days. 131 tracked threats reference CWE-122 directly or through a CVE it covers; the most recent is “OpenJDK / Oracle Java SE Compiler Memory Corruption Vulnerability (CVE-2026-114938) - Patch Recommendation” (2026-11-18). Affected products concentrate in Microsoft (145), Google (29), Adobe (15), among 45 vendors in total.
Vulnerabilities (CVEs)
Showing 40 of 252 CVEs mapped to CWE-122, CISA KEV first, then by CVSS score.
- CVE-2023-27997 — CISA KEV · CVSS 9.8 critical · EPSS 85.6% · published 2023-06-13
- CVE-2019-3568 — CISA KEV · CVSS 9.8 critical · EPSS 39.1% · published 2019-05-14
- CVE-2026-94127 — CISA KEV · CVSS 9.8 critical · EPSS 1.3% · published 2026-09-22
- CVE-2009-3459 — CISA KEV · CVSS 8.8 high · EPSS 86.5% · published 2009-10-13
- CVE-2023-4911 — CISA KEV · CVSS 7.8 high · EPSS 81.4% · published 2023-10-03
- CVE-2023-28252 — CISA KEV · CVSS 7.8 high · EPSS 48.9% · published 2023-04-11
- CVE-2026-53362 — CISA KEV · CVSS 7.8 high · EPSS 0.5% · published 2026-07-04
- CVE-2026-85880 — CISA KEV · CVSS 7.8 high · published 2026-09-08
- CVE-2025-25249 — CISA KEV · CVSS 7.4 high · EPSS 1.6% · published 2026-01-13
- CVE-2026-89126 — CVSS 10 critical · EPSS 0.4% · published 2026-11-10
- CVE-2026-47291 — CVSS 9.8 critical · EPSS 21.5% · published 2026-06-09
- CVE-2026-70242 — CVSS 9.8 critical · EPSS 1.5% · published 2026-10-13
- CVE-2024-49775 — CVSS 9.8 critical · EPSS 1.4% · published 2024-12-16
- CVE-2026-70291 — CVSS 9.8 critical · EPSS 1.3% · published 2026-10-13
- CVE-2026-97016 — CVSS 9.8 critical · EPSS 1.1% · published 2026-10-13
- CVE-2024-33698 — CVSS 9.8 critical · EPSS 1.0% · published 2024-09-10
- CVE-2026-69845 — CVSS 9.8 critical · EPSS 1.0% · published 2026-09-08
- CVE-2026-112393 — CVSS 9.8 critical · EPSS 1.0% · published 2026-10-19
- CVE-2026-41096 — CVSS 9.8 critical · EPSS 0.9% · published 2026-05-12
- CVE-2026-50518 — CVSS 9.8 critical · EPSS 0.9% · published 2026-07-14
- CVE-2026-55010 — CVSS 9.8 critical · EPSS 0.9% · published 2026-07-14
- CVE-2026-56159 — CVSS 9.8 critical · EPSS 0.9% · published 2026-07-14
- CVE-2026-67631 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-67643 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69276 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69408 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69431 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69493 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69496 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69586 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69590 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69715 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69769 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69824 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-69829 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-78509 — CVSS 9.8 critical · EPSS 0.9% · published 2026-09-08
- CVE-2026-112403 — CVSS 9.8 critical · EPSS 0.9% · published 2026-10-19
- CVE-2026-39919 — CVSS 9.8 critical · EPSS 0.8% · published 2026-09-15
- CVE-2026-102175 — CVSS 9.8 critical · EPSS 0.7% · published 2026-10-14
- CVE-2026-112398 — CVSS 9.8 critical · EPSS 0.6% · published 2026-10-19
Affected vendors
Threat activity
131 tracked threats cite CWE-122; the 25 most recent are listed.
- OpenJDK / Oracle Java SE Compiler Memory Corruption Vulnerability (CVE-2026-114938) - Patch RecommendationCRITICAL
- Oracle November 2026 CSPU: 655 Patches Covering ~640 Vulnerabilities Across 21 Products (incl. CVE-2026-114938 'Java4Shell' AVX-512 Base64 Heap Overflow)CRITICAL
- Chrome 158 Fixes 204 Vulnerabilities Including Six Critical Code Execution Flaws (CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975)CRITICAL
- Atlassian November 2026 Security Bulletin: 318 vulnerability entries across Jira, Confluence, Bitbucket, Bamboo, Crowd, Fisheye and Crucible (52 critical), plus Confluence Axis RCE CVE-2026-90436CRITICAL
- F5 BIG-IP: Six Critical Data-Plane Stack Buffer Overflows (CVE-2026-123637, CVE-2026-121805, CVE-2026-120292, CVE-2026-120285, CVE-2026-116953, CVE-2026-120722) Crash TMM, May Allow RCECRITICAL
- Java 17 Unauthenticated RCE (CVE-2026-114938) Reported as Oracle Ships 11 Java SE Fixes in November 2026 CPUCRITICAL
- Ransomware Ecosystem Professionalization: Akira, Qilin, Play Business-Style Operations and Sicarii AI-Assembled Variant Lacking Working DecryptorMEDIUM
- Kaspersky ICS CERT: APT and Financial Attacks on Industrial Organizations in Q2 2026 (DAEMON Tools Supply Chain, Iran-Linked PLC Attacks, ZionSiphon, INC Ransomware)HIGH
- FreeRDP client-side RCE chain (CVE-2026-91964 heap overflow + CVE-2026-91963 USB redirection heap disclosure) found via AI-agent vulnerability research workflowHIGH
- Multiple Windows Remote Desktop Client Vulnerabilities Allow Code Execution (CVE-2026-119934, CVE-2026-119858, CVE-2026-119390, CVE-2026-95964)HIGH
- Node.js November 2026 Security Releases Patch 16 Vulnerabilities (HTTP/2 crashes, HTTPS heap/TLS key leak CVE-2026-123864, TLS client-certificate auth bypass)HIGH
- Titan Quest: Anniversary Edition heap overflow in .lvl/.pfx file parsing exploited via malicious custom maps (no CVE)MEDIUM
- Google Chrome 157 Stable Update Fixes 83 Security Flaws Including 5 Critical Use-After-Free Bugs (CVE-2026-126885, CVE-2026-126895, CVE-2026-126879, CVE-2026-126846, CVE-2026-126911)CRITICAL
- Microsoft Patch Tuesday November 2026: ~1,095 vulnerabilities, 64 critical, one exploited Outlook NTLM-leak spoofing zero-day (CVE-2026-124194)CRITICAL
- Git Fixes 6 Vulnerabilities Enabling Code Execution via Cloned Repositories (CVE-2026-111760 et al.)HIGH
- Google Chrome XML Use-After-Free Zero-Day Exploited in the Wild (CVE-2026-125350)HIGH
- Notepad++ 8.9.9 Fixes 6 Vulnerabilities (Local Privilege Escalation, Command Dispatch, Heap Overflows in MIME Tools) - No CVEs AssignedMEDIUM
- CTO at NCSC Weekly Summary (week ending July 26, 2026): Cl0p PTC Windchill/FlexPLM exploitation (CVE-2026-12569), SonicWall SMA 1000 zero-days (CVE-2026-15409/CVE-2026-15410), and multi-actor state-linked activityHIGH
- SAP patches ICM2SHELL and PROXYGATE maximum severity flaws (CVE-2026-76964, CVE-2026-120017, CVE-2026-89103, CVE-2026-89126)CRITICAL
- Microsoft November 2026 Patch Tuesday: Outlook Zero-Day CVE-2026-124194 Exploited to Steal NTLM Hashes (1,235 Flaws Fixed)HIGH
- Microsoft November 2026 Patch Release: 1,093 Vulnerabilities Fixed, Outlook Spoofing Zero-Day CVE-2026-124194 Actively ExploitedCRITICAL
- Multiple Vulnerabilities in Google Chrome prior to 156.0.8078.73 (52 CVEs incl. CVE-2026-118306 FileSystem sandbox escape) - HKCERT Alert A26-10-59CRITICAL
- Multiple Vulnerabilities in Microsoft Edge (prior to 157.0.4341.42) - 27 Chromium CVEs - HK GovCERT A26-11-10HIGH
- CISA KEV Addition: SonicWall SonicOS SSLVPN Single-Factor Authentication / SAML Bypass Vulnerability (CVE-2026-19868)CRITICAL
- Multiple Vulnerabilities in Google Chrome (prior to 156.0.8078.79) - CVE-2026-76024 to CVE-2026-76031, CVE-2026-119260 to CVE-2026-119272HIGH
Mitigations
- General: Pre-design: Use a language or compiler that performs automatic bounds checking.
- Architecture and Design: Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Operation, Build and Compilation / Environment Hardening: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Operation, Build and Compilation / Environment Hardening: Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as "rebasing" (for Windows) and "prelinking" (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would…
- Implementation: Implement and perform bounds checking on input.
- Implementation / Libraries or Frameworks: Do not use dangerous functions such as gets. Look for their safe equivalent, which checks for the boundary.
- Operation: Use OS-level preventative functionality. This is not a complete solution, but it provides some defense in depth.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Fuzzing (effectiveness: High): Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
- Automated Dynamic Analysis (effectiveness: Moderate): Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.