Skip to main content
Menu
CVEs

CVE

53AIHub remote access to file previews

CVE-2026-130591EUVD-2026-127013GHSA-H7RF-8J2M-X5QJ

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 0.5.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.5.5.

Published
Last modified
Reference
Last checked
44/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: partial

Summary

53AIHub versions before 0.5.5 have a missing authentication flaw in their file preview endpoints. Remotely, without logging in, an attacker can request these endpoints and enumerate sequential numeric IDs to read raw knowledge-base files and stored file versions belonging to any enterprise tenant.

Written by a model from the sources below. Verify against them.

Original description

53AIHub before 0.5.5 contains a missing authentication vulnerability that allows unauthenticated attackers to read files by requesting /api/files/:file_id/preview and /api/file-version/:file_body_id without UserTokenAuth. Attackers can enumerate sequential numeric ids to read raw knowledge-base files and stored file versions belonging to any enterprise tenant.

cve.now Index

44Pcve.now Index 44 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 49 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.5.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130591 (53AIHub before 0.5.5 Missing Authentication via File Preview Endpoints), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130591 (entry last updated 2026-11-17):
Affected:
- 53AI 53AIHub: fixed in 0.5.5
Fixed versions: 0.5.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130591 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130591 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/53AI/53AIHub/commit/ed56bc01b4ec68183e7b03e56043bd1f3bf7ba5f
- https://github.com/53AI/53AIHub/issues/106
- https://github.com/53AI/53AIHub/releases/tag/v0.5.5
- https://github.com/53AI/53AIHub/blob/27bdc89569ab0a4a9a2042fc9d8f27bda5419ccc/api/router/api.go#L106-L109
- https://github.com/53AI/53AIHub/blob/27bdc89569ab0a4a9a2042fc9d8f27bda5419ccc/api/controller/file_preview.go#L42-L58
- https://www.vulncheck.com/advisories/53aihub-before-0.5.5-missing-authentication-via-file-preview-endpoints
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130591
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130591"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • 53AI 53AIHub

    fixed in 0.5.5

Evidence 9

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 6

  1. Patch
  2. Report
  3. Repository
  4. Repository
  5. Repository
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130591

Is CVE-2026-130591 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130591?

53AIHub: before 0.5.5.Source: cve.now feed data

How do I fix CVE-2026-130591?

Upgrade to a fixed version: 0.5.5.Source: cve.now feed data

More CVEs