# CVE-2026-73664: FreePBX: Authenticated Arbitrary SSH Key Injection via Backup Module

> An authenticated administrator can inject SSH keys to gain persistent shell access and execute arbitrary commands on the FreePBX server.

- **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:** 13 Aug 2026
- **Updated:** 14 Aug 2026

## What is CVE-2026-73664?

CVE-2026-73664 is a high-severity vulnerability in FreePBX backup, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

FreePBX is an open source IP PBX. From 17.0.5.34 until 17.0.11, the publicKeySave AJAX endpoint in Backup.class.php accepts an authenticated administrator's SSH public key and appends it to /home/asterisk/.ssh/authorized_keys for the asterisk system user without reliably enforcing backup-only command and source restrictions. The key grants persistent shell access that can execute arbitrary commands, access FreePBX and call data, modify system files, and disrupt services. This issue is fixed in version 17.0.11.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-284 (Improper Access Control), CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-73664 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73664 is a high-severity vulnerability in FreePBX backup, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73664 in the wild and no public exploit code.

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

## Sources

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

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