CVE-2026-55375: canto-saas-api OAuth Credentials Exposed Vulnerability

MODERATE
Advisory Identifier: GHSA-37pm-83g7-r22v
CVSS 5.3
CWE-598 CWE-209
Published
Advisory Summary

CVE-2026-55375 is a MODERATE (CVSS 5.3) oauth credentials exposed vulnerability (CWE-598: Use of HTTP Request With Sensitive Query String) affecting canto-saas-api libraries in the Packagist ecosystem. The issue involves oauth credentials exposed in url query string and exception messages. Remediation is available by upgrading affected packages to version 3.0.0.

CVE-2026-55375 at a Glance

CVE Identifier CVE-2026-55375
GHSA Identifier GHSA-37pm-83g7-r22v
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-598: Use of HTTP Request With Sensitive Query String
Affected Product canto-saas-api
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-55375

To remediate this vulnerability, upgrade all affected canto-saas-api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

jleehr/canto-saas-api fixed: 3.0.0
Upgrade jleehr/canto-saas-api to 3.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for jleehr/canto-saas-api

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-55375, inspect your project dependencies for canto-saas-api:

inspect dependencies for jleehr/canto-saas-api

Analyze the terminal output to locate any version of canto-saas-api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-598: Use of HTTP Request With Sensitive Query String, where the web application uses an http method to process a request, but the request includes sensitive information in the query string. In canto-saas-api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary In affected versions, the OAuth2 token request sends `app_id`, `app_secret`, `refresh_token` and `code` as URL query parameters of the POST request to `https://oauth.<domain>/oauth/api/oauth2/token`. Request URLs are commonly recorded in access logs, proxy logs and APM traces, so the application secret and refresh token can be persisted in plain text outside the application's control. In addition, when the token request fails, the Guzzle exception message — which contains the full request URI including the credentials — was passed unmodified into the `AuthorizationFailedException` thrown by `OAuth2::obtainAccessToken()`. Applications that log exceptions or forward them to error trackers (e.g. Sentry) may therefore have recorded the app secret in their logs. ## Impact An attacker with access to web server logs, proxy logs, APM tracing data or application error logs of a consumer of this library can obtain the Canto `app_secret`, `refresh_token` or authorization `code` and use them to obtain access tokens for the Canto tenant. ## Patches Fixed in 3.0.0: - OAuth credentials are sent in the form-encoded POST body instead of the URL query string (RFC 6749 §2.3.1). `OAuth2Request::getQueryParams()` now returns `null`; the parameters are available via `getFormParams()`. - Exception messages are sanitized before being rethrown: the values of `app_secret`, `refresh_token` and `code` are masked (including url-encoded, differently cased and JSON-embedded variants). ## Workarounds If you cannot upgrade: - Treat web server, proxy and APM logs of systems performing Canto OAuth requests as secret material and restrict access to them. - Catch `AuthorizationFailedException` in your application and strip the query string from the message before logging or forwarding it. If your logs may have been exposed, rotate the affected Canto app secret.

CVE-2026-55375 Affected canto-saas-api Versions

1 component(s)
Fixed Versions:
3.0.0
Product / Package Ecosystem Affected Versions Fixed Version
jleehr/canto-saas-api
Packagist
< 3.0.0
3.0.0

References

Frequently Asked Questions

What is CVE-2026-55375?
CVE-2026-55375 is a security vulnerability in canto-saas-api involving OAuth credentials exposed in URL query string and exception messages under CWE-598: Use of HTTP Request With Sensitive Query String.
Which canto-saas-api versions are affected?
Affected versions include releases prior to 3.0.0 across affected packages: jleehr/canto-saas-api.
What version fixes CVE-2026-55375?
Upgrading to 3.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is jleehr/canto-saas-api affected?
Yes, jleehr/canto-saas-api is affected in releases prior to 3.0.0. Upgrade your dependency to 3.0.0 or later.
What is the CVSS score of CVE-2026-55375?
CVE-2026-55375 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-55375?
CVE-2026-55375 is classified under CWE-598: Use of HTTP Request With Sensitive Query String (The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.).
How can I check Packagist dependencies for CVE-2026-55375?
Run the dependency tree command: 'inspect dependencies for jleehr/canto-saas-api'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-37pm-83g7-r22v",
  "modified" : "2026-06-19T14:16:41Z",
  "published" : "2026-06-19T14:16:41Z",
  "aliases" : [ "CVE-2026-55375" ],
  "summary" : "canto-saas-api: OAuth credentials exposed in URL query string and exception messages",
  "details" : "## Summary\n\n  In affected versions, the OAuth2 token request sends `app_id`, `app_secret`,\n  `refresh_token` and `code` as URL query parameters of the POST request to\n  `https://oauth.<domain>/oauth/api/oauth2/token`. Request URLs are commonly\n  recorded in access logs, proxy logs and APM traces, so the application secret\n  and refresh token can be persisted in plain text outside the application's\n  control.\n\n  In addition, when the token request fails, the Guzzle exception message —\n  which contains the full request URI including the credentials — was passed\n  unmodified into the `AuthorizationFailedException` thrown by\n  `OAuth2::obtainAccessToken()`. Applications that log exceptions or forward\n  them to error trackers (e.g. Sentry) may therefore have recorded the app\n  secret in their logs.\n\n  ## Impact\n\n  An attacker with access to web server logs, proxy logs, APM tracing data or\n  application error logs of a consumer of this library can obtain the Canto\n  `app_secret`, `refresh_token` or authorization `code` and use them to obtain\n  access tokens for the Canto tenant.\n\n  ## Patches\n\n  Fixed in 3.0.0:\n\n  - OAuth credentials are sent in the form-encoded POST body instead of the URL\n    query string (RFC 6749 §2.3.1). `OAuth2Request::getQueryParams()` now\n    returns `null`; the parameters are available via `getFormParams()`.\n  - Exception messages are sanitized before being rethrown: the values of\n    `app_secret`, `refresh_token` and `code` are masked (including url-encoded,\n    differently cased and JSON-embedded variants).\n\n  ## Workarounds\n\n  If you cannot upgrade:\n\n  - Treat web server, proxy and APM logs of systems performing Canto OAuth\n    requests as secret material and restrict access to them.\n  - Catch `AuthorizationFailedException` in your application and strip the query\n    string from the message before logging or forwarding it.\n\n  If your logs may have been exposed, rotate the affected Canto app secret.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "jleehr/canto-saas-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2.0.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/jleehr/canto-saas-api/security/advisories/GHSA-37pm-83g7-r22v"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/jleehr/canto-saas-api"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-209", "CWE-598" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-19T14:16:41Z",
    "nvd_published_at" : null
  }
}