<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 12:45:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-368893</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-368893</link>
      <description>EUVD-2026-368893</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-368893</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55375</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55375</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55375</guid>
    </item>
    <item>
      <title>GHSA-37pm-83g7-r22v — canto-saas-api: OAuth credentials exposed in URL query string and exception messages</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-37pm-83g7-r22v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: jleehr/canto-saas-api&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&amp;lt;domain&amp;gt;/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&amp;#39;s
  control.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in 3.0.0:&lt;/p&gt;
&lt;p&gt;- 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-enco…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: jleehr/canto-saas-api&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&amp;lt;domain&amp;gt;/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&amp;#39;s
  control.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in 3.0.0:&lt;/p&gt;
&lt;p&gt;- 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-enco…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-37pm-83g7-r22v</guid>
    </item>
  </channel>
</rss>
