CVE-2025-55739 api: Shared OAuth Signing Key Between Different Instances
Attackers can forge JWT tokens using a shared OAuth private key to bypass authentication and gain full API access in FreePBX.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2025-55739?
CVE-2025-55739 is a medium-severity vulnerability in FreePBX api, published on 4 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
api is a module for FreePBX@, which is an open source GUI that controls and manages Asterisk© (PBX). In versions lower than 15.0.13, 16.0.2 through 16.0.14, 17.0.1 and 17.0.2, there is an identical OAuth private key used across multiple systems that installed the same FreePBX RPM or DEB package. An attacker with access to the shared OAuth private key could forge JWT tokens, bypass authentication, and potentially gain full access to both REST and GraphQL APIs. Systems with the "api" module enabled, configured and previously activated by an administrator for remote inbound connections may be affected. This issue is fixed in versions 15.0.13, 16.0.15 and 17.0.3.
Which versions are affected by CVE-2025-55739?
How do I fix CVE-2025-55739?
No fix has been published for CVE-2025-55739 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-55739 being exploited?
There is no known exploitation of CVE-2025-55739 in the wild and no public exploit code.
Sources
Also known as GHSA-3r47-p39v-vqqf.