CVE-2026-134799

ByteStash 1.5.0 before 1.6.1 Login CSRF via OIDC Callback

Published Nov 22, 2026 CVSS 4.0 · 2.3 Low EPSS n/a KEV · Not listed
Description
ByteStash 1.5.0 before 1.6.1 contains a login cross-site request forgery vulnerability in the /api/auth/oidc/callback handler because OIDC state is not bound to the initiating browser. Attackers can start an OIDC login with their own account and lure victims into opening the withheld callback URL, logging them into the attacker's account to read saved snippets.

Analysis

AI-generated

Technical impact

The vulnerability exists in ByteStash versions 1.5.0 up through 1.6.0, where the OIDC callback endpoint does not tie the OIDC state parameter to the browser session that initiated the authentication request. This oversight allows an attacker to initiate an OAuth/OpenID Connect login using their own account, then trick a victim into visiting the callback URL generated for that login. When the victim's browser processes the callback, the application accepts it as a legitimate authentication response and logs the victim into the attacker's account. Once logged in, the victim's session is effectively hijacked, granting the attacker access to the victim's personal snippets and any other data available in the victim’s account. The primary impact is unauthorized access to user data via cross‑site request forgery; the severity score reflects a low risk of exploitation under normal circumstances.

Affected Systems

The affected software is ByteStash, a self‑hosted code snippet manager developed by jordan-dalby. Vulnerable releases include all 1.5.x versions and the 1.6.0 release. Version 1.6.1 and later contain the fix that binds OIDC state to the initiating browser session.

Risk and Exploitability

The CVSS score of 2.3 indicates low severity, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is not available, but the nature of the flaw—forcing a victim to visit a crafted callback URL—means exploitation requires social engineering or a malicious link. Because the OIDC state is not bound to the initiating browser session, an attacker can hijack a victim’s session only when the victim follows the link, so the immediate risk is moderate to low until active exploitation is observed. Nonetheless, organizations deploying ByteStash should address the issue promptly, especially if external OIDC providers are enabled.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade ByteStash to version 1.6.1 or later, which implements state binding for OIDC callbacks.
  • If an upgrade is delayed, temporarily disable OIDC authentication until the patch is applied.
  • Ensure that any custom OIDC callback handling verifies the state token against a stored session value before authenticating the user.

Generated by OpenCVE AI on November 22, 2026 at 22:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description ByteStash 1.5.0 before 1.6.1 contains a login cross-site request forgery vulnerability in the /api/auth/oidc/callback handler because OIDC state is not bound to the initiating browser. Attackers can start an OIDC login with their own account and lure victims into opening the withheld callback URL, logging them into the attacker's account to read saved snippets.
Title ByteStash 1.5.0 before 1.6.1 Login CSRF via OIDC Callback
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}

Subscriptions

No data.

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 22, 2026, 9:22 PM
Reserved
Nov 22, 2026, 5:09 PM
Status
Deferred
Published
Nov 22, 2026, 10:17 PM
Modified
Nov 22, 2026, 10:17 PM