CVE-2026-46515

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (6)

Auto-updated Aug 1, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Multiple read-tier tools expose admin-grade data and arbitrary GraphQL execution · Advisory · mwtcmi/frogman · GitHub

Affected: v1.6.3:

https://github.com/mwtcmi/frogman/security/advisories/GHSA-q4c4-5cr4-8q47
github_release Patch Available

v1.6.3 — security release (privilege-scoping advisory)

Patch available: mwtcmi/frogman v1.6.3

https://github.com/mwtcmi/frogman/releases/tag/v1.6.3
generic

DiagnoseTrunk: endpoint_raw response may include trunk auth credentials · Issue #25 · mwtcmi/frogman · GitHub

https://github.com/mwtcmi/frogman/issues/25
generic

Tighten permission level on sensitive read-tier tools · Issue #13 · mwtcmi/frogman · GitHub

https://github.com/mwtcmi/frogman/issues/13
github_commit Patch Available

commit b8a8bfc12b56 (mwtcmi/frogman)

Patch available: mwtcmi/frogman v1.6.3 (contains commit b8a8bfc12b56)

https://github.com/mwtcmi/frogman/commit/b8a8bfc12b564bcb77caef952873b9ffd4a98b00
github_commit Patch Available

commit 55ea257d5c24 (mwtcmi/frogman)

Patch available: mwtcmi/frogman v1.6.3 (contains commit 55ea257d5c24)

https://github.com/mwtcmi/frogman/commit/55ea257d5c24bc01c814a607faa7e76e86b111ec

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-02 03:14 UTCEG score recompute
  3. 2026-08-02 02:27 UTCEPSS rescore
  4. 2026-08-01 05:38 UTCEG score recompute
  5. 2026-08-01 04:16 UTCEPSS rescore
  6. 2026-07-30 18:59 UTCEG score recompute
  7. 2026-07-30 16:28 UTCEPSS rescore
  8. 2026-07-30 09:20 UTCEG score recompute
  9. 2026-07-30 05:01 UTCEG score recompute
  10. 2026-07-30 01:30 UTCEPSS rescore
  11. 2026-07-28 17:49 UTCEG score recompute
  12. 2026-07-28 15:36 UTCEPSS rescore
  13. 2026-07-27 15:16 UTCEG score recompute
  14. 2026-07-27 14:13 UTCEPSS rescore
  15. 2026-07-26 15:44 UTCEG score recompute
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 11:25 UTCEG score recompute
  19. 2026-07-25 14:18 UTCEPSS rescore
  20. 2026-07-24 14:17 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:17 UTCEG score recompute
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 6 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 02:34 UTCEG score recompute
  3. 2026-07-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 18:19 UTCEG score recompute
  6. 2026-07-16 18:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-46515?
CVE-2026-46515 is a critical vulnerability published on July 16, 2026. Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.3, PERMREAD access was sufficient to call fmlistmanagers, fmlistpinsets, fmshowcontext, fmgetmcpconfig, fmbackupstatus, fmwhoscalling, fmrunsavedquery, and fmdiagnosetrunk, exposing AMI manager secrets, outbound dial PINs,…
When was CVE-2026-46515 disclosed?
CVE-2026-46515 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46515 actively exploited?
CVE-2026-46515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46515?
CVE-2026-46515 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-46515?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46515, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46515

Explore →

Is Your Infrastructure Affected by CVE-2026-46515?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs