OliveTin Vulnerable to Unauthorized Action Output Disclosure via EventStream
CVE-2026-32102GHSA-228v-wc5r-j8m7
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/OliveTin/OliveTin 3000.10.2), 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
Go github.com/OliveTin/OliveTin
- Affected
- < 3000.10.2
- Fixed in
- 3000.10.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-228v-wc5r-j8m7 lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <3000.10.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-32102: 0.46% estimated exploitation activity in the next 30 days; percentile 39.74 (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 live EventStream broadcasts execution events and action output to authenticated dashboard subscribers without enforcing per-action authorization. A low-privileged authenticated user can receive output from actions they are not allowed to view, resulting in broken access control and sensitive information disclosure. I validated this on OliveTin 3000.10.2. Details The issue is in the live event streaming path. EventStream() only checks whether the caller may access the dashboard, then registers the user as a stream subscriber: - service/internal/api/api.go:776 After subscription, execution events are broadcast to all connected clients without checking whether each recipient is authorized to view logs for the action: - service/internal/api/api.go:846 OnExecutionStarted - service/internal/api/api.go:869 OnExecutionFinished - service/internal/api/api.go:1047 OnOutputChunk The event payload includes action output through: - service/internal/api/api.go:295…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-228v-wc5r-j8m7
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-32102 Advisory: OliveTin Vulnerable to Unauthorized Action Output Disclosure via EventStream IDs: CVE-2026-32102, GHSA-228v-wc5r-j8m7 Record: https://patchnext.com/advisories/cve-2026-32102 (revision 1, source checked 26 Oct 2026, 15:18 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.1) 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 3000.10.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/OliveTin/OliveTin: affected < 3000.10.2; fixed in 3000.10.2 ## 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-228v-wc5r-j8m7 (GitHub-reviewed advisory GHSA-228v-wc5r-j8m7 lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <3000.10.2) Commands are suggestions: review each one before running it.
Loading voting…