# CVE-2026-64949: Unrestricted File Upload Leading to Remote Code Execution in Admin Tools File Manager

> Authenticated attackers can upload malicious .phar files to achieve remote code execution due to an incomplete extension blacklist in the File Manager.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N/AU:Y/R:I/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-cqv6-4mfx-8cqr

## What is CVE-2026-64949?

CVE-2026-64949 is a high-severity vulnerability in Pandora FMS, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Incomplete extension blacklist in the File Manager module allows authenticated upload and execution of arbitrary .phar files. Affects Pandora FMS from 777 onwards.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

No fix has been published for CVE-2026-64949 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64949 being exploited?

There is no known exploitation of CVE-2026-64949 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64949 is a high-severity vulnerability in Pandora FMS, published on 1 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64949 in the wild and no public exploit code.

Affected product: Pandora FMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-64949/ (Markdown: https://insights.sbomify.com/CVE-2026-64949/index.md)
```

## Sources

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

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