CVE-2026-55375: jleehr canto-saas-api · Generation of Error Message Containing Sensitive Information
Affects jleehr canto-saas-apiSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.0.0 when convenient.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade canto-saas-api and jleehr/canto-saas-api to 3.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jleehrcanto-saas-api | Affected
| Fixed in
|
Packagistjleehr/canto-saas-apipkg:composer/jleehr/canto-saas-apiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to canto-saas-api version 3.0.0 or later, where this issue is fixed by removing sensitive credentials from URL query strings and error messages. Until the upgrade is applied, restrict access to logs, proxy logs, APM traces, and error trackers to trusted personnel only to minimize exposure. Patch status is confirmed fixed in version 3.0.0.
Description
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.