jleehr canto-saas-api up to 2.x OAuth2 Request getQueryParams app_id/app_secret/refresh_token/code missing encryption

Summaryinfo

A vulnerability has been found in jleehr canto-saas-api up to 2.x and classified as problematic. This vulnerability affects the function OAuth2Request::getQueryParams of the component OAuth2 Request Handler. This manipulation of the argument app_id/app_secret/refresh_token/code causes missing encryption. This vulnerability is tracked as CVE-2026-55375. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in jleehr canto-saas-api up to 2.x. Affected by this vulnerability is the function OAuth2Request::getQueryParams of the component OAuth2 Request Handler. The manipulation of the argument app_id/app_secret/refresh_token/code with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. The summary by CVE is:

canto-saas-api is a PHP library for interacting with the Canto SaaS API. Prior to version 3.0.0, OAuth2Request::getQueryParams() places app_id, app_secret, refresh_token, and code in the URL query string of token POST requests, allowing access logs, proxy logs, and APM traces to persist the credentials in plaintext. When a token request fails, OAuth2::obtainAccessToken() also passes the credential-bearing Guzzle request URI into AuthorizationFailedException, so application logs and error trackers can record the same secrets. An attacker with access to affected telemetry can obtain Canto credentials and use them to request access tokens for the tenant. This issue is fixed in version 3.0.0.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-55375 since 06/16/2026. The exploitation appears to be difficult. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.

Upgrading to version 3.0.0 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Automation Software

Vendor

• jleehr

Name

• canto-saas-api

Version

• 2.x

Website

• Product: https://github.com/jleehr/canto-saas-api/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion