CVE-2026-73085

Audiobookshelf: Refresh Token Accepted on Resource Endpoints

Published Aug 11, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Audiobookshelf is a self-hosted audiobook and podcast server. Prior to 2.36.0, the jwtAuthCheck function in server/auth/TokenManager.js treats JWTs with the refresh token type as bearer access tokens on API and WebSocket resource endpoints such as /api/me instead of restricting them to /auth/refresh, allowing refresh tokens to authenticate as the associated users. This issue is fixed in version 2.36.0.

Analysis

AI-generated

Technical impact

Audiobookshelf, a self‑hosted audiobook and podcast server, treats JWTs marked as refresh tokens as bearer access tokens on protected API and WebSocket endpoints such as /api/me. As a result, any user possessing a valid refresh token can impersonate that user on any resource endpoint, bypassing the intended separation between access and refresh token usage. The vulnerability is an authentication flaw (CWE‑287) that allows an attacker who obtains a victim’s refresh token to gain unauthorized access to the victim’s account data and actions.

Affected Systems

Audiobookshelf self‑hosted server from all releases before version 2.36.0. The issue is fixed starting with v2.36.0, so any deployment running a version earlier than 2.36.0 is vulnerable.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. The EPSS score is less than 1 %, showing a low probability of exploitation as of the current data set, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is an attacker who already has a victim’s refresh token—obtained through phishing, credential stuffing, or other means—using it to authenticate API requests. Because the flaw only impacts authenticated users, a successful exploit requires possession of a token, but once in hand it provides full user privileges and therefore a high potential impact.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the 2.36.0 release or later to fix the refresh‑token handling bug.
  • Revoke all existing refresh tokens and force users to log in again so that any compromised tokens are invalidated.
  • Verify that the deployment uses secure transport (HTTPS) and monitor authentication logs for anomalous use of refresh tokens.

Generated by OpenCVE AI on August 12, 2026 at 20:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Advplyr
Advplyr audiobookshelf
Vendors & Products Advplyr
Advplyr audiobookshelf
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Audiobookshelf is a self-hosted audiobook and podcast server. Prior to 2.36.0, the jwtAuthCheck function in server/auth/TokenManager.js treats JWTs with the refresh token type as bearer access tokens on API and WebSocket resource endpoints such as /api/me instead of restricting them to /auth/refresh, allowing refresh tokens to authenticate as the associated users. This issue is fixed in version 2.36.0.
Title Audiobookshelf: Refresh Token Accepted on Resource Endpoints
Weaknesses CWE-287
References
Metrics cvssV4_0

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

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 11, 2026, 6:39 PM
Reserved
Aug 10, 2026, 7:37 PM
Status
Deferred
Published
Aug 11, 2026, 5:19 PM
Modified
Oct 24, 2026, 3:10 PM