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 — 3 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
53%
KEV
Not listed

Published

August 24, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 15, 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 47× in last 7d / 202× 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.

Showing the most recent 100 of 202 total refreshes for this CVE.

  1. 2026-09-21 02:49 UTCGHSA enrichment
  2. 2026-09-20 22:31 UTCEG score recompute
  3. 2026-09-20 22:31 UTCGHSA enrichment
  4. 2026-09-20 18:12 UTCGHSA enrichment
  5. 2026-09-20 13:45 UTCGHSA enrichment
  6. 2026-09-20 09:27 UTCGHSA enrichment
  7. 2026-09-20 05:09 UTCGHSA enrichment
  8. 2026-09-20 00:51 UTCGHSA enrichment
  9. 2026-09-19 20:32 UTCGHSA enrichment
  10. 2026-09-19 16:14 UTCEG score recompute
  11. 2026-09-19 16:14 UTCGHSA enrichment
  12. 2026-09-19 11:56 UTCGHSA enrichment
  13. 2026-09-19 07:38 UTCGHSA enrichment
  14. 2026-09-19 03:18 UTCGHSA enrichment
  15. 2026-09-18 23:00 UTCEG score recompute
  16. 2026-09-18 23:00 UTCGHSA enrichment
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-18 18:43 UTCGHSA enrichment
  19. 2026-09-18 14:25 UTCGHSA enrichment
  20. 2026-09-18 10:06 UTCGHSA enrichment
  21. 2026-09-18 05:48 UTCGHSA enrichment
  22. 2026-09-18 01:30 UTCGHSA enrichment
  23. 2026-09-17 21:12 UTCEG score recompute
  24. 2026-09-17 21:12 UTCGHSA enrichment
  25. 2026-09-17 13:08 UTCGHSA enrichment
Show 75 more
  1. 2026-09-17 08:33 UTCGHSA enrichment
  2. 2026-09-17 04:14 UTCGHSA enrichment
  3. 2026-09-16 23:56 UTCGHSA enrichment
  4. 2026-09-16 19:38 UTCGHSA enrichment
  5. 2026-09-16 14:15 UTCEG score recompute
  6. 2026-09-16 14:15 UTCGHSA enrichment
  7. 2026-09-16 14:07 UTCEPSS rescore
  8. 2026-09-16 09:27 UTCEG score recompute
  9. 2026-09-16 09:27 UTCGHSA enrichment
  10. 2026-09-16 05:14 UTCEPSS rescore
  11. 2026-09-16 03:57 UTCGHSA enrichment
  12. 2026-09-15 23:36 UTCGHSA enrichment
  13. 2026-09-15 18:45 UTCGHSA enrichment
  14. 2026-09-15 14:20 UTCGHSA enrichment
  15. 2026-09-15 10:01 UTCGHSA enrichment
  16. 2026-09-15 05:43 UTCEG score recompute
  17. 2026-09-15 05:43 UTCGHSA enrichment
  18. 2026-09-15 01:05 UTCGHSA enrichment
  19. 2026-09-14 20:47 UTCGHSA enrichment
  20. 2026-09-14 16:29 UTCGHSA enrichment
  21. 2026-09-14 12:07 UTCGHSA enrichment
  22. 2026-09-14 07:50 UTCGHSA enrichment
  23. 2026-09-14 03:32 UTCGHSA enrichment
  24. 2026-09-13 23:14 UTCGHSA enrichment
  25. 2026-09-13 18:57 UTCGHSA enrichment
  26. 2026-09-13 14:35 UTCGHSA enrichment
  27. 2026-09-13 10:17 UTCGHSA enrichment
  28. 2026-09-13 05:59 UTCGHSA enrichment
  29. 2026-09-13 01:41 UTCGHSA enrichment
  30. 2026-09-12 21:23 UTCGHSA enrichment
  31. 2026-09-12 17:05 UTCEG score recompute
  32. 2026-09-12 17:05 UTCGHSA enrichment
  33. 2026-09-12 15:00 UTCEPSS rescore
  34. 2026-09-12 12:47 UTCGHSA enrichment
  35. 2026-09-12 08:29 UTCGHSA enrichment
  36. 2026-09-12 04:11 UTCGHSA enrichment
  37. 2026-09-11 23:53 UTCGHSA enrichment
  38. 2026-09-11 19:35 UTCGHSA enrichment
  39. 2026-09-11 15:17 UTCEG score recompute
  40. 2026-09-11 15:17 UTCGHSA enrichment
  41. 2026-09-11 14:52 UTCEPSS rescore
  42. 2026-09-11 10:59 UTCEG score recompute
  43. 2026-09-11 10:59 UTCGHSA enrichment
  44. 2026-09-11 09:36 UTCEPSS rescore
  45. 2026-09-11 06:40 UTCGHSA enrichment
  46. 2026-09-11 02:22 UTCGHSA enrichment
  47. 2026-09-10 22:04 UTCGHSA enrichment
  48. 2026-09-10 17:45 UTCGHSA enrichment
  49. 2026-09-10 13:27 UTCEG score recompute
  50. 2026-09-10 13:27 UTCGHSA enrichment
  51. 2026-09-10 09:34 UTCEPSS rescore
  52. 2026-09-10 09:09 UTCGHSA enrichment
  53. 2026-09-10 04:51 UTCGHSA enrichment
  54. 2026-09-10 00:33 UTCGHSA enrichment
  55. 2026-09-09 18:42 UTCGHSA enrichment
  56. 2026-09-09 14:24 UTCGHSA enrichment
  57. 2026-09-09 10:06 UTCGHSA enrichment
  58. 2026-09-09 05:48 UTCGHSA enrichment
  59. 2026-09-09 01:31 UTCEG score recompute
  60. 2026-09-09 01:31 UTCGHSA enrichment
  61. 2026-09-08 22:00 UTCEPSS rescore
  62. 2026-09-08 14:20 UTCGHSA enrichment
  63. 2026-09-08 04:15 UTCGHSA enrichment
  64. 2026-09-07 23:56 UTCGHSA enrichment
  65. 2026-09-07 19:39 UTCEG score recompute
  66. 2026-09-07 19:39 UTCGHSA enrichment
  67. 2026-09-07 16:01 UTCEPSS rescore
  68. 2026-09-07 15:21 UTCGHSA enrichment
  69. 2026-09-07 10:11 UTCGHSA enrichment
  70. 2026-09-07 05:52 UTCGHSA enrichment
  71. 2026-09-07 01:33 UTCGHSA enrichment
  72. 2026-09-06 21:14 UTCGHSA enrichment
  73. 2026-09-06 16:56 UTCEG score recompute
  74. 2026-09-06 16:56 UTCGHSA enrichment
  75. 2026-09-06 13:47 UTCEPSS rescore

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, with the most recent update on September 8, 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 47.2% 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.