# CVE-2026-130591: 53AIHub before 0.5.5 Missing Authentication via File Preview Endpoints


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-h7rf-8j2m-x5qj

## What is CVE-2026-130591?

CVE-2026-130591 is a high-severity vulnerability in 53AIHub, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-130591?

1 open source package ship an affected version, including 53ai/53aihub.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `53ai/53aihub` | GitHub | `pkg:github/53ai/53aihub` | All versions | 0.5.5 |

## How do I fix CVE-2026-130591?

Upgrade 53ai/53aihub to 0.5.5 or later.

## Is CVE-2026-130591 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130591 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130591 and fix it if it is affected.

What it is: CVE-2026-130591 is a high-severity vulnerability in 53AIHub, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130591 exists.

Affected packages and fixed versions:
- 53ai/53aihub (GitHub): affected all versions; fixed in 0.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130591/ (Markdown: https://insights.sbomify.com/CVE-2026-130591/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130591
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130591
- OSV: https://osv.dev/vulnerability/CVE-2026-130591

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130591/
Summaries are generated and may contain mistakes; the official description above is the record.
