canto-saas-api: Authenticated API requests can be redirected via unencoded path variables

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-55374: 0.36% estimated exploitation activity in the next 30 days; percentile 29.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In affected versions, Request::buildRequestUrl() inserts path variables into the request URL without URL encoding (implode('/', $pathVariables)). All request classes implementing getPathVariables() are affected, e.g. GetContentDetailsRequest (scheme, contentId). If a consuming application passes untrusted input (such as an ID taken from an HTTP request parameter) as a path variable, characters like ../, ? or

are sent verbatim and can change the path of the resulting API request.

Impact An attacker who controls a path variable value can redirect the library's authenticated request — the Bearer access token is attached in AbstractEndpoint::sendRequest() — to a different API endpoint of the same Canto instance, causing unintended reads or writes with the privileges of the configured app. The impact depends on how the consuming application sources path variable values; applications that only pass trusted, validated IDs are not exploitable.

Patches Fixed in 3.0.0: every…

Published by the source

19 Jun 2026, 14:13 UTC

Last modified by the source

19 Jun 2026, 14:13 UTC

Source last checked

26 Oct 2026, 14:49 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9qfv-wgh2-m6p8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55374

Advisory: canto-saas-api: Authenticated API requests can be redirected via unencoded path variables
IDs: CVE-2026-55374, GHSA-9qfv-wgh2-m6p8
Record: https://patchnext.com/advisories/cve-2026-55374 (revision 1, source checked 26 Oct 2026, 14:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jleehr/canto-saas-api 3.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist jleehr/canto-saas-api: affected <= 2.0.0; fixed in 3.0.0

## Suggested inspection (read-only)
- Packagist jleehr/canto-saas-api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jleehr/canto-saas-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9qfv-wgh2-m6p8 (GitHub-reviewed advisory GHSA-9qfv-wgh2-m6p8 lists affected ranges: Packagist jleehr/canto-saas-api >=0 <=2.0.0)

Commands are suggestions: review each one before running it.