<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:bytebase:bytebase:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3abytebasebytebase/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 22 Oct 2026 22:28:59 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3abytebasebytebase/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Bytebase: Authentication bypass via GitLab provider configuration (CVE-2022-51026)</title><link>https://feed.craftedsignal.io/briefs/2026-10-bytebase-auth-bypass/</link><pubDate>Thu, 22 Oct 2026 22:28:59 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-bytebase-auth-bypass/</guid><description>Bytebase versions prior to 1.0.1 are vulnerable to an authentication bypass in the GitLab login flow, allowing unauthenticated attackers to impersonate any user, including administrative accounts.</description><content:encoded><![CDATA[<p>Bytebase versions prior to 1.0.1 contain an authentication bypass vulnerability (CVE-2022-51026) in the <code>/api/auth/login/GITLAB_SELF_HOST</code> endpoint. The vulnerability exists because the application improperly trusts client-supplied GitLab provider configuration. An attacker can supply a malicious <code>instanceUrl</code> pointing to a server they control, which returns a fabricated active user response. Bytebase uses this response to generate session tokens, enabling the attacker to impersonate arbitrary users or create new accounts with elevated privileges.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated attackers to gain unauthorized access to the Bytebase instance by impersonating existing users, including the Owner role, or by creating new members.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Bytebase to version 1.0.1 or later immediately.</li>
<li>Review access logs and audit trails for unexpected authentication events or suspicious user creations within Bytebase if the instance was exposed during the vulnerable period.</li>
<li>Disable GitLab self-hosted authentication providers if they are not actively required for environment workflows.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category></item></channel></rss>