Security readout for executives and security teams
Plain-English summary
mpush v0.8.1 gateway servers may allow a remote attacker to take control by sending a malicious broadcast message. Successful exploitation could expose data, alter systems, and interrupt service. The supplied record rates this vulnerability critical, but does not identify a vendor patch or confirm real-world exploitation.
Executive priority
Treat this as an immediate exposure-assessment and containment priority. Internet-facing or broadly reachable mpush v0.8.1 gateways warrant urgent action because the stated outcome is unauthenticated remote code execution. Escalate suspected compromise to incident response. Patch availability is not established by the supplied sources.
Technical view
CVE-2026-79574 is classified as CWE-94 code injection in the mpush v0.8.1 gateway server. The supplied CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges or user interaction required, with high confidentiality, integrity, and availability impact. The public metadata does not clarify the vulnerable component, prerequisites, or affected configurations.
Likely exposure
Exposure is most likely where mpush v0.8.1 gateway servers are network-reachable and process broadcast messages. The supplied affected-product metadata is incomplete, listing vendor and product as unavailable, so organizations should confirm deployments through software inventories, container images, dependency records, and service ownership data.
Exploitation context
The cited researcher report describes arbitrary code execution through a crafted broadcast message. The CVSS vector indicates remote, unauthenticated exploitation with low complexity. However, CVE-2026-79574 is not listed as KEV in the supplied bundle, and no cited evidence confirms active exploitation or a public weaponized exploit.
Researcher notes
The record provides a concise vulnerability claim, CWE-94 classification, and critical CVSS vector, but limited affected-product and remediation detail. Validate version provenance, gateway reachability, broadcast-message trust boundaries, and process behavior. Avoid assuming versions beyond 0.8.1 are affected or fixed without authoritative evidence.
Mitigation direction
- Identify and prioritize all mpush v0.8.1 gateway deployments.
- Restrict gateway access to trusted networks and authenticated clients where operationally feasible.
- Limit or disable broadcast-message processing until vendor guidance is reviewed.
- Check upstream or vendor guidance for a confirmed patched release or supported mitigation.
- Increase monitoring around exposed gateways until remediation is verified.
Validation and detection
- Confirm deployed mpush versions using inventories, manifests, images, and dependency records.
- Determine whether gateway services are reachable from untrusted networks.
- Review configurations and access controls governing broadcast-message submission.
- Inspect gateway and host telemetry for unusual message processing, crashes, or spawned processes.
- Verify any upgrade or mitigation against published vendor guidance before closing the finding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-79574 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/fangtang7/CVE/blob/main/mpush/rce.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.