# CVE-2026-90770: Spug through 3.4.0 Remote Code Execution via ping_check

> Authenticated attackers can execute arbitrary commands by injecting shell metacharacters into monitor addresses in the Spug platform.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-h5c4-vc34-6jcv

## What is CVE-2026-90770?

CVE-2026-90770 is a high-severity command injection vulnerability in openspug spug, published on 13 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-90770?


## How do I fix CVE-2026-90770?

No fix has been published for CVE-2026-90770 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90770 being exploited?

There is no known exploitation of CVE-2026-90770 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90770 and fix it if it is affected.

What it is: CVE-2026-90770 is a high-severity command injection vulnerability in openspug spug, published on 13 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90770 in the wild and no public exploit code.

Affected product: openspug spug. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90770/ (Markdown: https://insights.sbomify.com/CVE-2026-90770/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90770
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90770
- OSV: https://osv.dev/vulnerability/CVE-2026-90770

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90770/
Summaries are generated and may contain mistakes; the official description above is the record.