Skip to content
Noroxi
OSV ecosystem advisory

GHSA-wcr3-9x4c-f5gj: Blnk has an API key authorization bypass in owner and scope enforcement

High—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Fixed version: github.com/blnkfinance/blnk (Go) 0.14.3.

Low priority for now. Upgrade to github.com/blnkfinance/blnk (Go) 0.14.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

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 - create a new API key with broader scopes than the caller’s own scopes The patched version changes this behavior for non-master API keys: - the effective owner is derived from the authenticated API key - caller-supplied owner values are no longer trusted for authorization decisions - cross-owner key operations are rejected with `403 Forbidden` - requested scopes must be covered by the caller’s existing scopes - master-key behavior is unchanged ## Impact A non-master API key with access to API key management endpoints could potentially perform unauthorized key-management operations across owners or escalate its permissions by creating a new API key with broader scopes. Deployments using API keys for programmatic key creation, listing, or revocation should upgrade. ## Affected versions Versions up to and including `v0.14.2` are affected. ## Patched versions This issue is fixed in `v0.14.3`. Users should upgrade to `v0.14.3` or later. ## Workarounds If developers cannot upgrade their applications immediately, restrict access to API key management endpoints to trusted master keys only. Where possible, disable or block non-master API key access to key creation, listing, and revocation endpoints until the patched version is deployed. ## Credits Blank thanks @Shivam8584 for identifying and fixing this issue.

Published
Jun 26, 2026
Updated
Jul 7, 2026
EPSS
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-wcr3-9x4c-f5gj

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
Gogithub.com/blnkfinance/blnk

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/blnkfinance/blnkbefore 0.14.30.14.3

Same product

Go: all records

Other highest-scoring records for the same primary product.

  • GO-2026-5823Blnk has an API key authorization bypass in owner and scope enforcement in github.com/blnkfinance/blnk
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/blnkfinance/blnk0.14.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records