Skip to main content
VulnerabilityPublished

CVE-2026-47713: Mintplex-Labs anything-llm · Improper Authorization

Affects Mintplex-Labs anything-llmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.0 Low : upgrade to 1.13.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.13.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 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 anything-llm and mintplex-labs/anything-llm to 1.13.0.

Affected software

ProductAffectedFixed in
Mintplex-Labsanything-llmAffected
  • <1.13.0
Fixed in
  • 1.13.0
GitHubmintplex-labs/anything-llmpkg:github/mintplex-labs/anything-llmOther threatsAffected
  • <1.13.0
Fixed in
  • 1.13.0

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

AI-suggested

Upgrade AnythingLLM to version 1.13.0 or later, where this improper authorization vulnerability is fixed. Patch status is not explicitly stated beyond this version fix, so users should verify with the vendor for any additional guidance. No other mitigations are indicated.

Description

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. Prior to 1.13.0, an approved mobile device token created in single-user mode can survive single-user -> multi-user migration even when the device record has userId = null. In multi-user mode, that stale token is still accepted by the mobile authentication middleware. Because no user is attached to the request, downstream mobile handlers fall back to unscoped data-access branches and return workspaces and workspace content without per-user filtering. This permits a pre-migration mobile token to enumerate a workspace assigned only to another user and retrieve victim-owned thread metadata and chat content in multi-user mode. This vulnerability is fixed in 1.13.0.

References

Community reviews

Loading reviews…