OliveTin has crash on NPE by calling APIs with invalid bindings or log references

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary An unauthenticated attacker can trigger server-side panics by first creating an execution log entry with a nil binding via StartActionByGet (invalid action ID), then calling KillAction or RestartAction on that tracking ID. This causes a nil-pointer dereference in API handlers and results in repeated per-request panics (Empty reply from server), enabling denial of service through panic/log/CPU amplification. Details The issue is caused by this flow: 1. StartActionByGet accepts arbitrary actionId and still calls executor: - service/internal/api/api.go:239 2. Executor stores a log entry before binding validation: - service/internal/executor/executor.go:519 3. If binding is nil, execution stops, but the log entry remains: - service/internal/executor/executor.go:781 4. KillAction dereferences execReqLogEntry.Binding.Action without checking Binding: - service/internal/api/api.go:79 5. RestartAction has the same unsafe dereference: - service/internal/api/api.go:1285 Because the…

Published by the source

5 Mar 2026, 20:54 UTC

Last modified by the source

5 Mar 2026, 20:54 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fwhj-785h-43hh

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

# Patch Next advisory brief: GHSA-fwhj-785h-43hh

Advisory: OliveTin has crash on NPE by calling APIs with invalid bindings or log references
IDs: GHSA-fwhj-785h-43hh
Record: https://patchnext.com/advisories/ghsa-fwhj-785h-43hh (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.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-20260304225158-bb14c5da3e64. A vendor fix does not mean a deployment is fixed.

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

## 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-fwhj-785h-43hh (GitHub-reviewed advisory GHSA-fwhj-785h-43hh lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260304225158-bb14c5da3e64)

Commands are suggestions: review each one before running it.