CVE-2026-90770
Received Received - Intake

Remote Code Execution in Spug via Monitor Address Injection

Vulnerability report for CVE-2026-90770, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-13

Last updated on: 2026-09-13

Assigner: VulnCheck

Description

Spug through 3.4.0 contains a remote code execution vulnerability in the ping_check function that interpolates user-supplied monitor addresses directly into shell commands without validation. Authenticated users with monitor permissions can inject shell metacharacters via the /monitor/run_test/ endpoint to execute arbitrary commands as the Spug process user.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-13
Last Modified
2026-09-13
Generated
2026-09-13
AI Q&A
2026-09-13
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
spug spug 3.4.0
openspug spug 3.4.0
openspug spug to 3.4.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-78 The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a remote code execution (RCE) flaw in Spug version 3.4.0 or earlier. It occurs in the ping_check function where user-supplied monitor addresses are directly inserted into shell commands without validation. Authenticated users with monitor permissions can inject shell metacharacters via the /monitor/run_test/ endpoint to execute arbitrary commands as the Spug process user.

Detection Guidance

To detect this vulnerability, check if Spug version 3.4.0 or earlier is running on your system. Inspect the ping_check function in spug_api/apps/monitor/executors.py for use of shell=True in subprocess.run calls. Monitor network traffic for suspicious requests to the /monitor/run_test/ endpoint with payloads containing shell metacharacters.

Impact Analysis

An attacker with monitor permissions could execute arbitrary OS commands on the Spug server. This may lead to full system compromise, unauthorized access to sensitive data like SSH keys or database credentials, and potential lateral movement within the network. Since monitor permissions are often granted to operations staff, non-administrative users could gain full control over the Spug management server.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. It may result in data breaches, unauthorized disclosure of personal or health information, and failure to implement adequate security controls, potentially leading to regulatory penalties and compliance violations.

Mitigation Strategies

Upgrade Spug to a version that fixes the ping command injection vulnerability. Replace shell=True with safe parameterized command construction in the ping_check function. Validate host addresses using strict regex and ipaddress validation. Remove permissions for monitor.monitor.add and monitor.monitor.edit from non-trusted users until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-90770. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart