bytebase Flaw (CVE-2022-51026) Rated CVSS 9.3
A newly published critical vulnerability in bytebase carries a CVSS score of 9.3. Here is what is affected and how to respond.
Key points
- CVE-2022-51026 affects bytebase.
- CVSS 9.3 (Critical).
- No exploitation confirmed yet.
A critical security flaw tracked as CVE-2022-51026 has been published in the National Vulnerability Database for bytebase, with a CVSS base score of 9.3.
At a glance
- CVE
- CVE-2022-51026
- Product
- bytebase
- CVSS
- 9.3 Critical
- Weakness
- CWE-290
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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 versions
| Vendor | Product | Versions |
|---|---|---|
| Bytebase | bytebase | before 1.0.1 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2022-51026
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2022-51026?
CVE-2022-51026 is a CWE-290 vulnerability in bytebase.
How severe is CVE-2022-51026?
It has a CVSS score of 9.3 Critical.
Is CVE-2022-51026 being exploited?
There is no public confirmation of exploitation at the time of publication.
