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.

How does O3 Security protect against GHSA-5r3p-6rj5-7937?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5r3p-6rj5-7937 can be triaged on real exposure rather than presence alone.

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.

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 March 4, 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

GHSA-5r3p-6rj5-7937 — bytebase

Fix: bytebase/bytebase@a578ed5

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

Bytebase vulnerable to Improper Authentication

Published

Mar 2, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, 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

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.

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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5r3p-6rj5-7937 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5r3p-6rj5-7937. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-5r3p-6rj5-7937 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works