go package report

Is github.com/authorizerdev/authorizer safe?

4 known vulnerabilities, worst severity CRITICAL.

cvss
9.3

how bad it is if exploited, out of 10

epss
0.30%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-h29v-hj44-q8cv, the advisory selected below

// advisories

GHSA-h29v-hj44-q8cv

CRITICALCVE-2026-54072

The /authorize endpoint accepts any redirecturi without validating it against AllowedOrigins. When responsetype=token or responsetype=idtoken, the server appends accesstoken, idtoken, and refreshtoken as query parameters and issues a 302 redirect to the attacker-supplied URL. An unauthenticated attacker can obtain the required clientid from the public /graphql?query={meta{clientid}} endpoint.

Affected
< 0.0.0-20260409051328-bd3f5baf6d3d, >=0, <0.0.0-20260409051328-bd3f5baf6d3d
Fixed in
0.0.0-20260409051328-bd3f5baf6d3d
Weakness
CWE-601
Published
2026-07-10
Source
github

GHSANVDMITREreference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so go packages are not covered.

Checked 2026-09-22 at 01:28 UTC. The most recent advisory here was published 2026-08-14. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is github.com/authorizerdev/authorizer safe? go package security report | CyberXYZ