/

CVE-2026-79574

Severity:

CRITICAL RISK

(9.8)

Code Injection (CWE-94) in mpush Gateway Server v0.8.1

CVE-2026-79574

Deferred

Vulnerability type

Category:

Code Injection

CWE:

CWE-94

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical code injection vulnerability in the mpush v0.8.1 gateway server allows crafted broadcast messages to reach an unsafe execution path. An attacker who can submit such a message may execute arbitrary code in the gateway server's runtime context.

Affected context

The issue occurs in the mpush v0.8.1 gateway server when it processes broadcast messages. Risk depends on the gateway being reachable through an exposed messaging interface and on crafted message content reaching a code-execution sink without adequate validation or isolation.

Exploit preconditions

  • Attack surface: The mpush gateway server's broadcast-message handling interface
  • Required access: Ability to send or cause delivery of a crafted broadcast message; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the crafted message by the gateway server
  • Why exploitation is possible: Message-controlled data can reach an execution path that permits arbitrary code to run in the server process

Why this happens

The underlying bug is an unsafe flow of externally influenced broadcast-message data into a code execution mechanism. This behavior maps to CWE-94: Improper Control of Generation of Code, where input is interpreted as executable code rather than treated strictly as data. Insufficient validation, encoding, or separation between message content and execution logic can create this condition.

Potential impact

  • An attacker may execute arbitrary code with the privileges of the gateway process
  • The attacker could access or modify gateway-hosted data
  • The service may be disrupted or used to affect connected clients
  • Compromise could enable lateral movement, credential exposure, or further application tampering

General mitigation guidance

Mitigation generally focuses on preventing message data from reaching dynamic evaluation or execution paths.

Common defensive patterns include:

  • Treating broadcast content strictly as data and removing dynamic evaluation of message fields
  • Applying allowlist-based validation and constrained schemas to message structures
  • Separating templating or command functionality from untrusted message handling
  • Running the gateway with least privilege and limiting filesystem, network, and process permissions
  • Enforcing authentication and authorization for broadcast operations
  • Using process isolation and restrictive runtime policies to reduce the impact of server compromise

How teams detect issues like this

Detection approaches may include:

  • Static analysis for dynamic evaluation, command construction, runtime compilation, or interpreter invocation using message-derived values
  • Code review checks tracing broadcast-message fields into execution, templating, or deserialization APIs
  • Runtime monitoring for unexpected child processes, shell activity, outbound connections, or anomalous gateway behavior
  • Policy enforcement requiring schemas, allowlists, authorization checks, and security tests for broadcast interfaces
  • Automated code review tools can help identify untrusted data flows into code-execution sinks

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/mpush/rce.md

Frequently asked

questions

It may be remotely exploitable when the gateway's broadcast-message interface is network reachable and an attacker can submit or influence messages. The exact scope depends on exposure and access controls.

The description does not establish whether authentication is required. The relevant prerequisite is authorization to send, publish, or otherwise cause processing of a crafted broadcast message.

Remove dynamic code execution from message processing and ensure broadcast content is handled only as validated data using strict schemas and allowlists.

Enforce authorization at the messaging boundary, perform security-focused data-flow reviews, apply least privilege, and monitor for unexpected process execution by the gateway.

Find out what's already
exploitable in your codebase.