# CVE-2026-73699: FileRun < 2026.3.0 PHP Object Injection via Perms::getPerms()

> Authenticated attackers with database write access can achieve arbitrary code execution via PHP object injection in FileRun permissions handling.

- **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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-3xv5-w7r3-9wj8

## What is CVE-2026-73699?

CVE-2026-73699 is a high-severity unsafe deserialization vulnerability in FileRun, published on 10 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

FileRun before 2026.3.0 contains a PHP object injection vulnerability that allows authenticated attackers to execute arbitrary code by exploiting incorrect options passed to unserialize() in the Perms::getPerms() method, where a positional array is used instead of the required named-key array to disable class instantiation. Attackers with database write access can inject a serialized gadget chain into the permissions table columns processed on every authenticated page load to write arbitrary files, such as PHP webshells, to web-accessible paths.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-73699 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73699 is a high-severity unsafe deserialization vulnerability in FileRun, published on 10 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73699 exists.

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

## Sources

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

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