CVE-2026-19874

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 24, 2026

Advisory Details (3)

Auto-updated Aug 24, 2026
No patch confirmed yet. Sources: cert.
cert

VU#728712 - Konami's Metal Gear Online 3 contains a heap-based buffer overflow

https://www.kb.cert.org/vuls/id/728712
cert

VU#728712 - Konami's Metal Gear Online 3 contains a heap-based buffer overflow

https://kb.cert.org/vuls/id/728712
generic

CWE - CWE-122: Heap-based Buffer Overflow (4.20)

https://cwe.mitre.org/data/definitions/122.html

Vendor Advisories for CVE-2026-19874(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 50× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:25 UTCEG score recompute
  2. 2026-08-30 02:25 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 22:07 UTCGHSA enrichment
  5. 2026-08-29 17:49 UTCGHSA enrichment
  6. 2026-08-29 13:25 UTCGHSA enrichment
  7. 2026-08-29 09:04 UTCGHSA enrichment
  8. 2026-08-29 04:44 UTCGHSA enrichment
  9. 2026-08-29 00:26 UTCEG score recompute
  10. 2026-08-29 00:26 UTCGHSA enrichment
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 16:26 UTCGHSA enrichment
  13. 2026-08-28 11:32 UTCGHSA enrichment
  14. 2026-08-28 07:13 UTCGHSA enrichment
  15. 2026-08-28 02:51 UTCGHSA enrichment
  16. 2026-08-27 22:32 UTCGHSA enrichment
  17. 2026-08-27 18:14 UTCEG score recompute
  18. 2026-08-27 18:14 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-27 13:04 UTCGHSA enrichment
  21. 2026-08-27 08:43 UTCGHSA enrichment
  22. 2026-08-27 04:25 UTCGHSA enrichment
  23. 2026-08-27 00:05 UTCGHSA enrichment
  24. 2026-08-26 19:46 UTCGHSA enrichment
  25. 2026-08-26 15:29 UTCEG score recompute
Show 25 more
  1. 2026-08-26 15:29 UTCGHSA enrichment
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-26 11:10 UTCGHSA enrichment
  4. 2026-08-26 06:51 UTCGHSA enrichment
  5. 2026-08-26 02:32 UTCGHSA enrichment
  6. 2026-08-25 22:15 UTCGHSA enrichment
  7. 2026-08-25 17:56 UTCEG score recompute
  8. 2026-08-25 17:56 UTCGHSA enrichment
  9. 2026-08-25 13:48 UTCEPSS rescore
  10. 2026-08-25 13:38 UTCGHSA enrichment
  11. 2026-08-25 09:20 UTCGHSA enrichment
  12. 2026-08-25 05:02 UTCGHSA enrichment
  13. 2026-08-25 00:44 UTCEG score recompute
  14. 2026-08-25 00:44 UTCGHSA enrichment
  15. 2026-08-24 20:26 UTCGHSA enrichment
  16. 2026-08-24 20:11 UTCEG score recompute 9.10
  17. 2026-08-24 20:11 UTCGHSA enrichment
  18. 2026-08-24 20:11 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  19. 2026-08-24 17:19 UTCGHSA enrichment
  20. 2026-08-24 17:18 UTCNVD update
  21. 2026-08-24 16:25 UTCGHSA enrichment
  22. 2026-08-24 16:17 UTCMITRE cvelistV5
  23. 2026-08-24 15:23 UTCNVD update
  24. 2026-08-24 15:16 UTCEG score recompute
  25. 2026-08-24 15:16 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCalicealys/mgo3-rce
    First seen Jul 8, 2026

    CVE-2026-19874

    Open source ↗

Frequently asked(5)

What is CVE-2026-19874?
CVE-2026-19874 is a critical vulnerability published on August 24, 2026. 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 "kicknum" to determine the number of…
When was CVE-2026-19874 disclosed?
CVE-2026-19874 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19874 actively exploited?
CVE-2026-19874 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.7% of all scored CVEs.
What is the CVSS score of CVE-2026-19874?
CVE-2026-19874 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19874?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19874, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19874

Explore →

Is Your Infrastructure Affected by CVE-2026-19874?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.