Quick answers
- Is CVE-2026-94619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94619 being exploited in the wild.
- How severe is CVE-2026-94619?
- Medium severity, with a CVSS score of 5.9, published 6 November 2026.
- Which products and versions are affected?
- FileGator before 7.15.0; filegator/filegator (Packagist) <= 7.14.4, ECOSYSTEM:introduced=0,fixed=7.15.0.
- Is there a fix for CVE-2026-94619?
- Yes. filegator/filegator (Packagist): upgrade to 7.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94619 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-94619?
- Check whether you run FileGator or filegator/filegator (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- filegator/filegator (Packagist): upgrade to 7.15.0 or later
composer require filegator/filegator:^7.15.0
Technical details
The vulnerability exists in UploadController.php where the request-supplied resumableFilename parameter is used directly as a key into shared temporary storage without user namespacing. An authenticated attacker with upload permission can set resumableTotalChunks and resumableTotalSize to zero to trigger a read of pre-existing temporary files with an attacker-chosen name, then store or delete them in their own directory. The flaw affects multi-user deployments with distinct per-user home directories and is mitigated by restricting access to the tmpfs temporary directory itself.
Affected products
- FileGator FileGator before 7.15.0
Identifiers
- CVE-2026-94619
- GHSA-44r8-3p76-84mw
Timeline
- 2026-11-06: disclosed