CVE-2026-46515
PERM_READ API in Frogman (<1.6.3) leaks PBX secrets, dialplans, PINs and AMI data.
Is CVE-2026-46515 being exploited?
Not confirmed. CVE-2026-46515 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-46515?
CVE-2026-46515 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46515?
Yes. A fix has been recorded for CVE-2026-46515. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46515 affect?
CVE-2026-46515 affects Frogman < 1.6.3, Frogman MCP/HTTP API endpoints, Asterisk AMI integrations exposing SIP fields. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46515?
Upgrade to Frogman v1.6.3, rotate exposed credentials, restrict API access and audit PBX logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
PERM_READ access allows exfiltration of AMI manager secrets, SIP credentials, dialplans, PINs, backup paths, CDRs and arbitrary saved GraphQL queries enabling credential theft, fraud, lateral movement.
Immediate action required
- affected< 1.6.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.