Canto Saas Api
Approved changes feed: RSS · Atom
cpe:2.3:a:jleehr:canto-saas-api:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Jleehr (c9b94749-6f88-5b56-8594-7ee26d81088c) |
|---|---|
| Product | Canto Saas Api (5fd4ff67-73ed-50ca-a31d-40ea697c12b2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-55375 |
vulnerable | 2026-09-16 04:33:12.595807 |
canto-saas-api: OAuth credentials exposed in URL query string and exception messages
MEDIUM (5.3)
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.
Published: 2026-09-15T17:30:29.992Z
Updated: 2026-09-15T19:05:49.862Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.