Blnk has an API key authorization bypass in owner and scope enforcement

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Blnk API key endpoints had an authorization issue that allowed non-master API keys to perform key-management actions outside their intended authorization boundary. In affected versions, API key operations trusted caller-controlled request values for owner and scope decisions. As a result, a non-master API key could potentially manage keys for another owner by supplying a different owner value, or create a more privileged API key by requesting broader scopes than it already had. This has been fixed by deriving the effective owner from the authenticated API key and enforcing scope coverage checks when creating new keys. Details The API key authorization flow previously trusted request data supplied by the caller when deciding which owner a key-management operation applied to and which scopes could be granted. This meant a non-master API key could potentially: - create API keys for another owner - list API keys belonging to another owner - revoke API keys belonging to another owner -…

Published by the source

26 Jun 2026, 22:31 UTC

Last modified by the source

26 Jun 2026, 22:31 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wcr3-9x4c-f5gj

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

# Patch Next advisory brief: GHSA-wcr3-9x4c-f5gj

Advisory: Blnk has an API key authorization bypass in owner and scope enforcement
IDs: GHSA-wcr3-9x4c-f5gj
Record: https://patchnext.com/advisories/ghsa-wcr3-9x4c-f5gj (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: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/blnkfinance/blnk 0.14.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/blnkfinance/blnk: affected <= 0.14.2; fixed in 0.14.3

## Suggested inspection (read-only)
- Go github.com/blnkfinance/blnk: 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/blnkfinance/blnk.
- 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-wcr3-9x4c-f5gj (GitHub-reviewed advisory GHSA-wcr3-9x4c-f5gj lists affected ranges: Go github.com/blnkfinance/blnk >=0 <=0.14.2)

Commands are suggestions: review each one before running it.