# CVE-2026-130596: FusionPBX through 5.6.5 Path Traversal via Fax Email Attachment Filename


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/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-8hhv-xwfp-wcp5

## What is CVE-2026-130596?

CVE-2026-130596 is a medium-severity vulnerability in fusionpbx, published on 17 Nov 2026. 

### Official description

FusionPBX through 5.6.5 contains a path traversal vulnerability in app/fax/fax_emails.php that allows unauthenticated remote attackers to write files by using a crafted MIME attachment filename. Attackers can email the polled fax mailbox with a spoofed authorized From address and use ../ sequences in the filename to create or overwrite web-server-writable files with .pdf/.tif content.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

1 open source package ship an affected version, including fusionpbx/fusionpbx.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `fusionpbx/fusionpbx` | GitHub | `pkg:github/fusionpbx/fusionpbx` | All versions to 5.6.5 | None |

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

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

## Is CVE-2026-130596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130596 is a medium-severity vulnerability in fusionpbx, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130596 in the wild and no public exploit code.

Affected packages and fixed versions:
- fusionpbx/fusionpbx (GitHub): affected all versions up to 5.6.5; no fix listed

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

## Sources

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

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