Skip to main content
VulnerabilityPublished

CVE-2026-73085: advplyr audiobookshelf · Improper Authentication

Affects advplyr audiobookshelfSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.36.0 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.36.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade audiobookshelf and advplyr/audiobookshelf to 2.36.0.

Affected software

ProductAffectedFixed in
advplyraudiobookshelfAffected
  • <2.36.0
Fixed in
  • 2.36.0
GitHubadvplyr/audiobookshelfpkg:github/advplyr/audiobookshelfOther threatsAffected
  • <2.36.0
Fixed in
  • 2.36.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Audiobookshelf to version 2.36.0 or later, where this improper authentication issue is fixed. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor stating the issue is resolved in 2.36.0.

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.

References

Community reviews

Loading reviews…