How severe is GHSA-5r3p-6rj5-7937?

No CVSS score has been assigned to GHSA-5r3p-6rj5-7937 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5r3p-6rj5-7937?

GHSA-5r3p-6rj5-7937 affects the following packages: github.com/bytebase/bytebase (Go). Ecosystems affected: Go.

How do I fix GHSA-5r3p-6rj5-7937?

Update github.com/bytebase/bytebase to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5r3p-6rj5-7937 is resolved across your whole dependency graph.

How do I detect GHSA-5r3p-6rj5-7937 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bytebase/bytebase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5r3p-6rj5-7937 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5r3p-6rj5-7937 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5r3p-6rj5-7937 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5r3p-6rj5-7937?

GHSA-5r3p-6rj5-7937 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5r3p-6rj5-7937?

GHSA-5r3p-6rj5-7937 is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5r3p-6rj5-7937 published, and has it been updated?

GHSA-5r3p-6rj5-7937 was published on March 2, 2026 and was last updated on October 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Bytebase vulnerable to Improper AuthenticationGHSA-5r3p-6rj5-7937

Fix: bytebase/bytebase@a578ed5

GHSA-5r3p-6rj5-7937 is a CWE-290 vulnerability in github.com/bytebase/bytebase. A fix is available for github.com/bytebase/bytebase — see the affected versions and patch details below.

Also known asCVE-2022-51026

Published

Mar 2, 2026

Updated

Oct 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5r3p-6rj5-7937.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/bytebase/bytebase

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Bytebase 0.12.0 before 1.0.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to log in as any user. The flaw stems from trusting client-supplied GitLab provider configuration in the POST /api/auth/login/GITLAB_SELF_HOST endpoint. Attackers can set instanceUrl to a server they control that returns an active user with a chosen email. Bytebase then issues session tokens for that principal, letting attackers impersonate existing users including the Owner or create new members.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bytebase/bytebase`	all versions	1.0.1`go get github.com/bytebase/bytebase@v1.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bytebase/bytebase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bytebase/bytebase to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5r3p-6rj5-7937 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact - GitLab login allows login by any user. - JWT auth token can be derived as long as the server isn't rebooted. - Developers can assign issues to non-admin/DBA users.

O3 Security · Impact-Aware SCA

Is GHSA-5r3p-6rj5-7937 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works