# CVE-2025-50946: OliveTin OS Command Injection vulnerability

> An OS command injection vulnerability in the Olivetin library allows attackers to execute arbitrary commands via the ParseRequestURI function.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-p3qf-84rg-jxfc, GO-2025-3886

## What is CVE-2025-50946?

CVE-2025-50946 is a medium-severity command injection vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS Command Injection in Olivetin 2025.4.22 Custom Themes via the ParseRequestURI function in service/internal/executor/arguments.go.

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

## Which versions are affected by CVE-2025-50946?

3 open source packages ship an affected version, including github.com/OliveTin/OliveTin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/OliveTin/OliveTin` | Go | All versions | None |
| `github.com/OliveTin/OliveTin` | Go | All versions to 0.0.0-20250502155356-8c073bf45fca | None |
| `github.com/OliveTin/OliveTin` | Go | All versions to 0.0.0-20250502155356-8c073bf45fca | None |

Products: Olivetin Olivetin.

## How do I fix CVE-2025-50946?

Upgrade to a fixed version.

## Is CVE-2025-50946 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50946 exists.

Public exploit code:

- Exploit script for CVE-2025-50946 (github_poc): https://github.com/runt1me/cve-2025-50946

## Other vulnerabilities in n/a

- [CVE-2026-27626](https://insights.sbomify.com/CVE-2026-27626/): OliveTin: OS Command Injection via `password` argument type and webhook JSON extraction bypasses shell safety checks (critical 10.0)
- [CVE-2026-30223](https://insights.sbomify.com/CVE-2026-30223/): OliveTin: JWT Audience Validation Bypass in Local Key and HMAC Modes (high 8.8)
- [CVE-2026-31817](https://insights.sbomify.com/CVE-2026-31817/): OliveTin's unsafe parsing of UniqueTrackingId can be used to write files (high 8.5)
- [CVE-2026-28342](https://insights.sbomify.com/CVE-2026-28342/): OliveTin: Unauthenticated Denial of Service via Memory Exhaustion in PasswordHash API Endpoint (high 7.5)
- [CVE-2026-28789](https://insights.sbomify.com/CVE-2026-28789/): OliveTin: Unauthenticated DoS via concurrent map writes in OAuth2 state handling (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50946 and fix it if it is affected.

What it is: CVE-2025-50946 is a medium-severity command injection vulnerability in n/a, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50946 exists.

Affected packages and fixed versions:
- github.com/OliveTin/OliveTin (Go): affected all versions; no fix listed
- github.com/OliveTin/OliveTin (Go): affected all versions up to 0.0.0-20250502155356-8c073bf45fca; no fix listed
- github.com/OliveTin/OliveTin (Go): affected all versions up to 0.0.0-20250502155356-8c073bf45fca; no fix listed

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-2025-50946/ (Markdown: https://insights.sbomify.com/CVE-2025-50946/index.md)
```

## Sources

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

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