Skip to main content
VulnerabilityPublished Updated

CVE-2026-89022: bookstackapp bookstack · Authentication Bypass by Spoofing

Affects bookstackapp bookstackSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical : upgrade to 26.05.5 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
9.1Critical
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 26.05.5
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 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 30 Oct 2026.

What to do

Upgrade bookstackapp bookstack to 26.05.5.

Affected software

ProductAffectedFixed in
bookstackappbookstackAffected
  • <26.05.5
Fixed in
  • 26.05.5
GitHubbookstackpkg:github/bookstackOther threatsAffected
  • <26.05.5
Fixed in
  • 26.05.5

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

AI-suggested

A fix is available in BookStack version 26.05.5. Users should upgrade to version 26.05.5 or later to remediate this vulnerability. No additional mitigations are specified.

Description

BookStack before 26.05.5 contains an authentication bypass vulnerability in its social login implementation that allows unauthenticated attackers to sign in as arbitrary users by authenticating through a different social provider sharing the same driver_id namespace. Attackers can authenticate at one enabled social provider using a user ID that matches an account linked to a different social provider, bypassing credential verification entirely because the SocialAuthService::handleLoginCallback query ignores the driver column when retrieving linked account records.

References

Community reviews

Loading reviews…