CVE-2026-55374: canto-saas-api Authenticated API Requests Can Be Vulnerability
MODERATECVE-2026-55374 is a MODERATE (CVSS 4.8) authenticated api requests can be vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting canto-saas-api libraries in the Packagist ecosystem. The issue involves authenticated api requests can be redirected via unencoded path variables. Remediation is available by upgrading affected packages to version 3.0.0.
CVE-2026-55374 at a Glance
Security Impact
CVSS: 4.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-55374
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.
Upgrade jleehr/canto-saas-api to 3.0.0
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-55374, 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. 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
CVE-2026-55374 Affected canto-saas-api Versions
1 component(s)| 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-55374?
Which canto-saas-api versions are affected?
What version fixes CVE-2026-55374?
Is jleehr/canto-saas-api affected?
What is the CVSS score of CVE-2026-55374?
What CWE is associated with CVE-2026-55374?
How can I check Packagist dependencies for CVE-2026-55374?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9qfv-wgh2-m6p8",
"modified" : "2026-06-19T14:13:55Z",
"published" : "2026-06-19T14:13:55Z",
"aliases" : [ "CVE-2026-55374" ],
"summary" : "canto-saas-api: Authenticated API requests can be redirected via unencoded path variables",
"details" : "## Summary\n\n In affected versions, `Request::buildRequestUrl()` inserts path variables into\n the request URL without URL encoding (`implode('/', $pathVariables)`). All\n request classes implementing `getPathVariables()` are affected, e.g.\n `GetContentDetailsRequest` (`scheme`, `contentId`).\n\n If a consuming application passes untrusted input (such as an ID taken from\n an HTTP request parameter) as a path variable, characters like `../`, `?` or\n `#` are sent verbatim and can change the path of the resulting API request.\n\n ## Impact\n\n An attacker who controls a path variable value can redirect the\n library's authenticated request — the Bearer access token is attached in\n `AbstractEndpoint::sendRequest()` — to a different API endpoint of the same\n Canto instance, causing unintended reads or writes with the privileges of the\n configured app. The impact depends on how the consuming application sources\n path variable values; applications that only pass trusted, validated IDs are\n not exploitable.\n\n ## Patches\n\n Fixed in 3.0.0: every path segment is encoded with `rawurlencode()` before\n being inserted into the request URL.\n\n ## Workarounds\n\n If you cannot upgrade, validate untrusted values before passing them to\n request classes, e.g. enforce an allowlist pattern such as\n `^[A-Za-z0-9_-]+$` for content IDs and schemes.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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-9qfv-wgh2-m6p8"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jleehr/canto-saas-api"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-74", "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-19T14:13:55Z",
"nvd_published_at" : null
}
}