# CVE-2026-8914: Command injection in Profile change function

> A lower privileged user can execute arbitrary commands as root via unsafe eval calls in the profile change function on Teltonika network devices.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-7p37-7qj9-8qff

## What is CVE-2026-8914?

CVE-2026-8914 is a high-severity command injection vulnerability in Teltonika Networks RUTOS, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Teltonika Networks RUTOS devices, running versions 7.22 through 7.23.2 and TSWOS devices running versions 1.09 through 1.09.1, due to unsafe calls to an eval function in rpc-profile, a vulnerability exists where a lower privileged user could perform command injection as the root user.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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


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

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

## Is CVE-2026-8914 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8914 is a high-severity command injection vulnerability in Teltonika Networks RUTOS, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8914 in the wild and no public exploit code.

Affected product: Teltonika Networks RUTOS. 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-8914/ (Markdown: https://insights.sbomify.com/CVE-2026-8914/index.md)
```

## Sources

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

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