CVE-2026-44237 FreePBX: Authenticated Access can lead to Subsequent OAuth2 Authentication Bypass in API Module

High 7.6 Published Updated

Attackers with a valid client_id can bypass OAuth2 authentication in FreePBX API to obtain access tokens without the correct secret.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-44237?

CVE-2026-44237 is a high-severity authentication bypass vulnerability in Sangoma Freepbx, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

FreePBX is an open source IP PBX. Prior to 17.0.8, the FreePBX api module's OAuth2 implementation does not sufficiently validate client credentials during token issuance. Knowledge of a valid client_id is required. The validateClient() method in ClientRepository.php unconditionally returns true, allowing any party with knowledge of a valid client_id to obtain OAuth2 access tokens without providing the correct client_secret. This vulnerability is fixed in 17.0.8.

Weakness: CWE-1390

Which versions are affected by CVE-2026-44237?

It affects 1 product.

Products include Sangoma Freepbx.

How do I fix CVE-2026-44237?

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

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-44237 being exploited?

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

All Sangoma Freepbx vulnerabilities

Sources

Also known as GHSA-vgjf-4h63-8vcc.

Is CVE-2026-44237 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free