CVE-2026-19874: Konami's Metal Gear Online 3 contains a heap-based buffer overflow
A heap-based buffer overflow vulnerability exists in Konami's Metal Gear Online 3, originating from improper validation of lobby data fields related to kicked players. The affected function processes a list of kicked player identifiers using the lobby data key "kick_num" to determine the number of entries, and individual kicked player IDs supplied via keys in the format "kicked_id_%i". The function does not validate that "kick_num" falls within the expected bounds. The game design limits matches to a maximum of 16 players, and the corresponding buffer for storing kicked player IDs is sized accordingly. If "kick_num" exceeds this limit, the function continues writing the provided player IDs past the end of the intended buffer and into adjacent memory regions. These adjacent regions contain Steam callback handler structures responsible for processing lobby data updates, lobby messages, and other related events. By supplying an oversized "kick_num" value and appropriate "kicked_id_%i" fields, an attacker can overwrite fields within the callback handler structures, including function pointers and callback argument values. Successful exploitation may enable control-flow hijacking, potentially allowing arbitrary code execution within the game process.
Security readout for executives and security teams
Plain-English summary
Metal Gear Online 3 version 1.1.2.8 can mishandle malicious lobby information, writing beyond an allocated memory buffer. This may crash or manipulate the game process and could potentially allow arbitrary code execution. The supplied sources identify no confirmed patch and provide no evidence of active exploitation.
Executive priority
Treat this as an urgent exposure-assessment item because the reported flaw is remotely reachable and may enable code execution without authentication or interaction. Prioritize inventory, vendor-guidance monitoring, and exposure reduction. Escalate immediately where affected systems process untrusted lobby data, while avoiding claims of active exploitation unsupported by the sources.
Technical view
The game trusts the lobby field "kick_num" without enforcing the 16-player limit, then stores attacker-supplied "kicked_id_%i" values in a fixed-size heap buffer. Excess entries can overwrite adjacent Steam callback structures, including function pointers and arguments, creating potential control-flow hijacking. The issue is classified as CWE-122 and scored CVSS 3.1 9.1.
Likely exposure
Confirmed scope is Konami Metal Gear Online 3 version 1.1.2.8. Systems running that version and processing attacker-controlled lobby data are potentially exposed. The bundle does not establish whether other versions, platforms, or configurations are affected.
Exploitation context
The reported path is network-accessible, requires no privileges or user interaction, and has low attack complexity according to the supplied CVSS vector. Successful exploitation could compromise integrity and availability of the game process. CVE-2026-19874 is not listed as KEV in the bundle, and no cited evidence confirms exploitation in the wild.
Researcher notes
The overwrite reportedly progresses from the kicked-player identifier array into adjacent Steam callback handler structures. Function-pointer and callback-argument corruption makes control-flow hijacking plausible, but the bundle does not document a working exploit, exploitation reliability, platform-specific protections, affected builds beyond 1.1.2.8, or a vendor fix. Validation should remain non-destructive.
Mitigation direction
Identify and prioritize systems running Metal Gear Online 3 version 1.1.2.8.
Check Konami and CERT/CC guidance for an official update or mitigation.
Apply any vendor-provided security update after appropriate testing.
Until guidance is available, limit affected-version exposure to untrusted multiplayer lobbies.
Preserve crash and security telemetry for investigation.
Validation and detection
Verify the installed game version on potentially affected systems.
Confirm whether version 1.1.2.8 can receive untrusted lobby data.
Review crash records for unusual failures during lobby updates or messaging.
Confirm vendor guidance has been reviewed and applicable updates deployed.
Recheck the CVE and CERT/CC records for revised scope or remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.