Skip to content

← Actionable
Medium, CVSS 4.3amended

OliveTin: StartActionAndWait Endpoints Bypass logs Permission and Return Action Output

CVE-2026-67439GHSA-jm28-2wcr-qf3h

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-20260708085316-e421780c9885), 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
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-67439: 0.43% estimated exploitation activity in the next 30 days; percentile 37.63 (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 The synchronous execution RPCs StartActionAndWait and StartActionByGetAndWait return the full LogEntry for the just-executed action without checking whether the caller is allowed to read that action's logs. OliveTin's ACL model separates exec from logs. A deployment can intentionally allow a user to run an action while denying access to its historical or live output. That separation is enforced in GetLogs, GetActionLogs, ExecutionStatus, and EventStream, but it is not enforced in the synchronous ...AndWait endpoints. As a result, any user who can execute an action through these endpoints can read the action output immediately even when the action's ACL explicitly sets logs:false. Details OliveTin defines separate per-action permissions: The normal log and streaming paths correctly enforce logs permission: That check is used by: - GetLogs - GetActionLogs - ExecutionStatus - EventStream However, the synchronous execution endpoints directly return the created LogEntry without…

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

    Amended from ghsa record GHSA-jm28-2wcr-qf3h

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6144

  3. Revision 1 · created ·

    Published from osv record GHSA-jm28-2wcr-qf3h

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-67439

Advisory: OliveTin: StartActionAndWait Endpoints Bypass `logs` Permission and Return Action Output
IDs: CVE-2026-67439, GHSA-jm28-2wcr-qf3h
Record: https://patchnext.com/advisories/cve-2026-67439 (revision 3, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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-20260708085316-e421780c9885. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/OliveTin/OliveTin: affected < 0.0.0-20260708085316-e421780c9885; fixed in 0.0.0-20260708085316-e421780c9885

## 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://osv.dev/vulnerability/GHSA-jm28-2wcr-qf3h (OSV record GHSA-jm28-2wcr-qf3h lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260708085316-e421780c9885 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6144 (OSV record GO-2026-6144 lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260708085316-e421780c9885 (fixed))
- Verified: https://github.com/advisories/GHSA-jm28-2wcr-qf3h (GitHub-reviewed advisory GHSA-jm28-2wcr-qf3h lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260708085316-e421780c9885)

Commands are suggestions: review each one before running it.

Loading voting…