Skip to main content
Menu
CVEs

CVE

OliveTin command injection in post-exec via shell hook

CVE-2026-75506EUVD-2026-129185Published Updated Summary written by a model

6.6MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3000.18.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3000.18.1.

Summary

OliveTin, a web interface for running predefined shell commands, has an OS command injection flaw in its post-execution `shellAfterCompleted` handling. A remote attacker who needs high-level privileges and no user action can run arbitrary commands as the OliveTin process user by injecting shell metacharacters through command output or the `ot_username` value in actions that configure `shellAfterCompleted`, even when the primary action uses exec-array mode.

Original description

OliveTin gives safe and simple access to predefined shell commands from a web interface. From 3000.0.0 until 3000.18.1, OliveTin passes attacker-influenceable output and ot_username values into shellAfterCompleted processing in service/internal/executor/executor.go without applying checkShellArgumentSafety, the shell-safety validation used for primary action execution. The same post-execution template path also expands exitCode without that validation, but the advisory does not establish attacker control of the exit-code value. When an action configures shellAfterCompleted with output or ot_username, shell metacharacters from command output, external data processed by an action, or a trusted-header username can become syntax in the command executed by the stepExecAfter path. This can execute arbitrary commands as the OliveTin process user, including when the primary action uses the safer exec-array mode. This issue is fixed in version 3000.18.1.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.6/10CVSS 6.6
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3000.18.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-75506 (OliveTin: Second-Order OS Command Injection via shellAfterCompleted), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-75506 (entry last updated 2026-11-18):
Affected:
- OliveTin OliveTin: from 3000.0.0, fixed in 3000.18.1
Fixed versions: 3000.18.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-75506 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75506 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OliveTin/OliveTin/security/advisories/GHSA-vc6p-m6vx-6cwq
- https://github.com/OliveTin/OliveTin/pull/1070
- https://github.com/OliveTin/OliveTin/pull/1088
- https://github.com/OliveTin/OliveTin/commit/4ef86abee7aac4e4ec4a3200c7ca491ca3501065
- https://github.com/OliveTin/OliveTin/commit/e5d29b68da66fd7f99072d6afd336dee2c28876c
- https://github.com/OliveTin/OliveTin/releases/tag/3000.17.0
- https://github.com/OliveTin/OliveTin/releases/tag/3000.18.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-75506
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75506"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • OliveTin OliveTin

    From 3000.0.0 · fixed in 3000.18.1

Evidence 9

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-75506

Is CVE-2026-75506 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-75506?

OliveTin: from 3000.0.0 before 3000.18.1.Source: cve.now feed data

How do I fix CVE-2026-75506?

Upgrade to a fixed version: 3000.18.1.Source: cve.now feed data

More CVEs