OliveTin: ValidateArgumentType API Endpoint's Missing Authentication Allows Action and Argument Enumeration

Exploitation

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

CVSS

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

EPSS

• CVE-2026-48709: 0.33% estimated exploitation activity in the next 30 days; percentile 26.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The ValidateArgumentType RPC endpoint in service/internal/api/api.go does not perform any authentication or authorization checks. Unlike all other data-returning API endpoints, it does not call auth.UserFromApiCall or checkDashboardAccess. When AuthRequireGuestsToLogin is enabled (the security-conscious configuration), this endpoint remains accessible to unauthenticated users and can be used as an oracle to enumerate valid action binding IDs and their argument configurations. Details Root Cause The ValidateArgumentType handler at service/internal/api/api.go:726 has no authentication check: Compare this with adjacent endpoints that DO have auth checks: Oracle Behavior The endpoint provides different responses based on whether the binding and argument exist: - Valid binding + valid argument: Returns {valid: true/false, description: "..."} (200 OK) - Valid binding + invalid argument: Returns CodeNotFound error - Invalid binding: Returns CodeNotFound error While the error…

Published by the source

24 Jun 2026, 17:41 UTC

Last modified by the source

24 Jun 2026, 17:41 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f637-w7p2-m7fx

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

# Patch Next advisory brief: CVE-2026-48709

Advisory: OliveTin: ValidateArgumentType API Endpoint's Missing Authentication Allows Action and Argument Enumeration
IDs: CVE-2026-48709, GHSA-f637-w7p2-m7fx
Record: https://patchnext.com/advisories/cve-2026-48709 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
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-20260521230847-a3865704c854. A vendor fix does not mean a deployment is fixed.

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

## 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-f637-w7p2-m7fx (GitHub-reviewed advisory GHSA-f637-w7p2-m7fx lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260521230847-a3865704c854)

Commands are suggestions: review each one before running it.