<?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>Fri, 02 Oct 2026 10:00:42 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0653 — De multiples vulnérabilités ont été découvertes dans Symfony. Certaines d'entre elles permettent à un attaquant de prov…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0653</link>
      <description>certfr-2026-avi-0653</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0653</guid>
    </item>
    <item>
      <title>EUVD-2026-337990</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337990</link>
      <description>EUVD-2026-337990</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337990</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48747</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48747</link>
      <description>&lt;p&gt;Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 7.4.13 and 8.0.13, MailomatRequestParser::validateSignature() parsed X-MOM-Webhook-Signature as algo=signature and passed the request-selected algorithm to hash_hmac(), allowing a signature algorithm downgrade instead of enforcing Mailomat&amp;#39;s documented SHA-256 webhook signature. This issue is fixed in versions 7.4.13 and 8.0.13.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 7.4.13 and 8.0.13, MailomatRequestParser::validateSignature() parsed X-MOM-Webhook-Signature as algo=signature and passed the request-selected algorithm to hash_hmac(), allowing a signature algorithm downgrade instead of enforcing Mailomat&amp;#39;s documented SHA-256 webhook signature. This issue is fixed in versions 7.4.13 and 8.0.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-48747</guid>
    </item>
    <item>
      <title>GHSA-rrj9-5q2j-4gvr — Symfony: Mailomat Mailer Webhook Parser Reads the HMAC Algorithm from the Request: Signature Algorithm Downgrade</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rrj9-5q2j-4gvr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: symfony/mailomat-mailer, Packagist: symfony/symfony&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Symfony\Component\Mailer\Bridge\Mailomat\Webhook\MailomatRequestParser::validateSignature()` parses the `X-MOM-Webhook-Signature` request header as `algo=signature` and passes the wire-supplied `$algo` directly to `hash_hmac()` when verifying the request against the configured webhook secret. The request therefore selects the HMAC primitive used to authenticate it.&lt;/p&gt;
&lt;p&gt;PHP&amp;#39;s `hash_hmac()` enforces only that the chosen algorithm is HMAC-compatible. That set still includes primitives with known cryptanalysis (`md4`, `md5`, `ripemd128`, `tiger128,3`, … — e.g. existential forgery of HMAC-MD4, Contini &amp;amp; Yin, ASIACRYPT 2006). This is the canonical algorithm-confusion shape, analogous to JWT `alg=none` / `alg=HS256` downgrades: any future cryptographic weakness in any HMAC primitive PHP exposes becomes immediately exploitable against a Mailomat webhook receiver, the moment an attacker is in a position to compute a signature for that primitive, without a code change on the Symfony side.&lt;/p&gt;
&lt;p&gt;Mailomat&amp;#39;s [documented webhook security](https://api.mailomat.swiss/docs/#tag/webhook-security) pins SHA-256; the parser did not.&lt;/p&gt;
&lt;p&gt;### Resolution&lt;/p&gt;
&lt;p&gt;`MailomatRequestParser::validateSignature()` now requires the signature header to be of the form `sha256=&amp;lt;hex&amp;gt;` and verifies the signature with HMAC-SHA256 keyed by the configured secret using a constant-time comparison. Any other algorithm declared on the wire (including the HMAC primitives PHP would otherwise accept) is rejected.&lt;/p&gt;
&lt;p&gt;The pat…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: symfony/mailomat-mailer, Packagist: symfony/symfony&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;`Symfony\Component\Mailer\Bridge\Mailomat\Webhook\MailomatRequestParser::validateSignature()` parses the `X-MOM-Webhook-Signature` request header as `algo=signature` and passes the wire-supplied `$algo` directly to `hash_hmac()` when verifying the request against the configured webhook secret. The request therefore selects the HMAC primitive used to authenticate it.&lt;/p&gt;
&lt;p&gt;PHP&amp;#39;s `hash_hmac()` enforces only that the chosen algorithm is HMAC-compatible. That set still includes primitives with known cryptanalysis (`md4`, `md5`, `ripemd128`, `tiger128,3`, … — e.g. existential forgery of HMAC-MD4, Contini &amp;amp; Yin, ASIACRYPT 2006). This is the canonical algorithm-confusion shape, analogous to JWT `alg=none` / `alg=HS256` downgrades: any future cryptographic weakness in any HMAC primitive PHP exposes becomes immediately exploitable against a Mailomat webhook receiver, the moment an attacker is in a position to compute a signature for that primitive, without a code change on the Symfony side.&lt;/p&gt;
&lt;p&gt;Mailomat&amp;#39;s [documented webhook security](https://api.mailomat.swiss/docs/#tag/webhook-security) pins SHA-256; the parser did not.&lt;/p&gt;
&lt;p&gt;### Resolution&lt;/p&gt;
&lt;p&gt;`MailomatRequestParser::validateSignature()` now requires the signature header to be of the form `sha256=&amp;lt;hex&amp;gt;` and verifies the signature with HMAC-SHA256 keyed by the configured secret using a constant-time comparison. Any other algorithm declared on the wire (including the HMAC primitives PHP would otherwise accept) is rejected.&lt;/p&gt;
&lt;p&gt;The pat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rrj9-5q2j-4gvr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-48747</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-48747</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: symfony, Ubuntu:Pro:18.04:LTS: symfony, Ubuntu:Pro:20.04:LTS: symfony, Ubuntu:Pro:22.04:LTS: symfony, Ubuntu:Pro:24.04:LTS: symfony, Ubuntu:25.10: symfony, Ubuntu:26.04:LTS: symfony&lt;/p&gt;
&lt;p&gt;Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 7.4.13 and 8.0.13, MailomatRequestParser::validateSignature() parsed X-MOM-Webhook-Signature as algo=signature and passed the request-selected algorithm to hash_hmac(), allowing a signature algorithm downgrade instead of enforcing Mailomat&amp;#39;s documented SHA-256 webhook signature. This issue is fixed in versions 7.4.13 and 8.0.13.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: symfony, Ubuntu:Pro:18.04:LTS: symfony, Ubuntu:Pro:20.04:LTS: symfony, Ubuntu:Pro:22.04:LTS: symfony, Ubuntu:Pro:24.04:LTS: symfony, Ubuntu:25.10: symfony, Ubuntu:26.04:LTS: symfony&lt;/p&gt;
&lt;p&gt;Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 7.4.13 and 8.0.13, MailomatRequestParser::validateSignature() parsed X-MOM-Webhook-Signature as algo=signature and passed the request-selected algorithm to hash_hmac(), allowing a signature algorithm downgrade instead of enforcing Mailomat&amp;#39;s documented SHA-256 webhook signature. This issue is fixed in versions 7.4.13 and 8.0.13.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-48747</guid>
    </item>
  </channel>
</rss>
