Skip to content

← Actionable
Critical, CVSS 9.9

OliveTin: OS Command Injection via password argument type and webhook JSON extraction bypasses shell safety checks

CVE-2026-27626GHSA-49gm-hh7w-wfvf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/OliveTin/OliveTin 0.0.0-20260222101908-4bbd2eab1532), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.9 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-27626: 0.64% estimated exploitation activity in the next 30 days; percentile 50.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary OliveTin's shell mode safety check (checkShellArgumentSafety) blocks several dangerous argument types but not password. A user supplying a password-typed argument can inject shell metacharacters that execute arbitrary OS commands. A second independent vector allows unauthenticated RCE via webhook-extracted JSON values that skip type safety checks entirely before reaching sh -c. Details Vector 1 — password type bypasses shell safety check (PR:L) service/internal/executor/arguments.go has two gaps: Shell execution at service/internal/executor/executorunix.go:18: A user supplies a password argument value of '; id; echo ' → sh -c interprets the shell metacharacters → arbitrary command execution. This is not the "admin already has access" pattern: OliveTin explicitly enforces an admin/user boundary where admins define commands and users only supply argument values. The password type is the documented, intended mechanism for user-supplied sensitive values. The safety check exists…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-49gm-hh7w-wfvf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27626

Advisory: OliveTin: OS Command Injection via `password` argument type and webhook JSON extraction bypasses shell safety checks
IDs: CVE-2026-27626, GHSA-49gm-hh7w-wfvf
Record: https://patchnext.com/advisories/cve-2026-27626 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/OliveTin/OliveTin 0.0.0-20260222101908-4bbd2eab1532. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/OliveTin/OliveTin: affected < 0.0.0-20260222101908-4bbd2eab1532; fixed in 0.0.0-20260222101908-4bbd2eab1532

## Suggested inspection (read-only)
- Go github.com/OliveTin/OliveTin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/OliveTin/OliveTin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-49gm-hh7w-wfvf (GitHub-reviewed advisory GHSA-49gm-hh7w-wfvf lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260222101908-4bbd2eab1532)

Commands are suggestions: review each one before running it.

Loading voting…