OliveTin has JWT Audience Validation Bypass in Local Key and HMAC Modes

Exploitation

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

CVSS

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

EPSS

• CVE-2026-30223: 0.33% estimated exploitation activity in the next 30 days; percentile 26.47 (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 When JWT authentication is configured using either: - authJwtPubKeyPath (local RSA public key), or - authJwtHmacSecret (HMAC secret), the configured audience value (authJwtAud) is not enforced during token parsing. As a result, validly signed JWT tokens with an incorrect aud claim are accepted for authentication. This allows authentication using tokens intended for a different audience/service. Details Affected Code File: jwt.go Lines: 51–59, 144–157, 161–168 Current Behavior Remote JWKS Mode (Correct): Audience validation is enforced. Local Public Key Mode (Vulnerable): No jwt.WithAudience() option is provided. HMAC Mode (Vulnerable): No jwt.WithAudience() option is provided. Why This Is Vulnerable: authJwtAud is ignored for authJwtPubKeyPath and authJwtHmacSecret modes, so wrong-audience tokens are accepted. PoC 1. Configure OliveTin Use a minimal config with JWT local key authentication: 2. Generate a Wrong-Audience Token This prints the $WRONGAUDTOKEN. 3. Test Without…

Published by the source

5 Mar 2026, 20:52 UTC

Last modified by the source

6 Mar 2026, 22:52 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g962-2j28-3cg9

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

# Patch Next advisory brief: CVE-2026-30223

Advisory: OliveTin has JWT Audience Validation Bypass in Local Key and HMAC Modes
IDs: CVE-2026-30223, GHSA-g962-2j28-3cg9
Record: https://patchnext.com/advisories/cve-2026-30223 (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: High (CVSS 8.8)
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-20260304231339-e97d8ecbd8d6. A vendor fix does not mean a deployment is fixed.

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

## 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-g962-2j28-3cg9 (GitHub-reviewed advisory GHSA-g962-2j28-3cg9 lists affected ranges: Go github.com/OliveTin/OliveTin >=0 <0.0.0-20260304231339-e97d8ecbd8d6)

Commands are suggestions: review each one before running it.