# CVE-2026-46515: Frogman: Multiple read-tier tools expose admin-grade data and arbitrary GraphQL execution

> Attackers with read access can expose sensitive secrets and execute arbitrary GraphQL queries in Frogman PBX control software.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-q4c4-5cr4-8q47

## What is CVE-2026-46515?

CVE-2026-46515 is a critical missing authorization vulnerability in mwtcmi frogman, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.3, PERM_READ access was sufficient to call fm_list_managers, fm_list_pinsets, fm_show_context, fm_get_mcp_config, fm_backup_status, fm_whos_calling, fm_run_saved_query, and fm_diagnose_trunk, exposing AMI manager secrets, outbound dial PINs, full Asterisk dialplan context, root SSH connection commands, backup artifact paths, CDR history, arbitrary saved GraphQL query execution, and raw AMI endpoint dumps containing SIP fields such as password, md5_cred, and oauth_secret. This issue is fixed in version 1.6.3.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-46515 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46515 is a critical missing authorization vulnerability in mwtcmi frogman, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46515 in the wild and no public exploit code.

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

## Sources

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

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