Skip to main content
VulnerabilityPublished

CVE-2026-55374: jleehr canto-saas-api · Injection

Affects jleehr canto-saas-apiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium : upgrade to 3.0.0 when convenient.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% 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:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
jleehrcanto-saas-apiAffected
  • <3.0.0
Fixed in
  • 3.0.0
GitHubjleehr/canto-saas-apipkg:github/jleehr/canto-saas-apiOther threatsAffected
  • <3.0.0
Fixed in
  • 3.0.0

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 properly encoding path segments. Until upgrading, ensure that all path variable inputs are strictly validated and trusted to prevent injection of special characters that could alter request URLs.

Description

canto-saas-api is a PHP library for interacting with the Canto SaaS API. Prior to version 3.0.0, Request::buildRequestUrl() joins values returned by Request::getPathVariables() without encoding individual path segments, including the scheme and contentId values used by GetContentDetailsRequest. When a consuming application supplies an untrusted path variable value, path traversal sequences, query delimiters, or fragment delimiters can change the destination endpoint before AbstractEndpoint::sendRequest() attaches the configured authentication token. An attacker who controls that path variable value through the consuming application can cause unintended reads or writes with the configured application's privileges on the same Canto instance, but applications that pass only trusted and validated identifiers are not exploitable. This issue is fixed in version 3.0.0.

References

Community reviews

Loading reviews…