<?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>Wed, 07 Oct 2026 15:06:39 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0508 — De multiples vulnérabilités ont été découvertes dans Moodle. Certaines d'entre elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0508</link>
      <description>certfr-2026-avi-0508</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0508</guid>
    </item>
    <item>
      <title>EUVD-2026-263923</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-263923</link>
      <description>EUVD-2026-263923</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-263923</guid>
    </item>
    <item>
      <title>fkie_cve-2025-14761</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-14761</link>
      <description>&lt;p&gt;Missing cryptographic key commitment in the AWS SDK for PHP may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an &amp;#34;instruction file&amp;#34; instead of S3&amp;#39;s metadata record.&lt;/p&gt;
&lt;p&gt;To mitigate this issue, upgrade AWS SDK for PHP to version 3.368.0 or later&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Missing cryptographic key commitment in the AWS SDK for PHP may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an &amp;#34;instruction file&amp;#34; instead of S3&amp;#39;s metadata record.&lt;/p&gt;
&lt;p&gt;To mitigate this issue, upgrade AWS SDK for PHP to version 3.368.0 or later&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-14761</guid>
    </item>
    <item>
      <title>GHSA-x8cp-jf6f-r4xh — AWS SDK for PHP's S3 Encryption Client has a Key Commitment Issue</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x8cp-jf6f-r4xh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: aws/aws-sdk-php&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;S3 Encryption Client for PHP is an open-source client-side encryption library used to facilitate writing and reading encrypted records to S3.&lt;/p&gt;
&lt;p&gt;When the encrypted data key (EDK) is stored in an &amp;#34;Instruction File&amp;#34; instead of S3&amp;#39;s metadata record, the EDK is exposed to an &amp;#34;Invisible Salamanders&amp;#34; attack  (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;### Background - Key Commitment&lt;/p&gt;
&lt;p&gt;There is a cryptographic property whereby under certain conditions, a single ciphertext can be decrypted into 2 different plaintexts by using different encryption keys. To address this issue, strong encryption schemes use what is known as &amp;#34;key commitment&amp;#34;, a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message.&lt;/p&gt;
&lt;p&gt;In older versions of S3EC, when customers are also using a feature called &amp;#34;Instruction File&amp;#34; to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object.  For such customers an attack that leverages the lack of key commitment is possible. A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C. Any future attem…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: aws/aws-sdk-php&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;S3 Encryption Client for PHP is an open-source client-side encryption library used to facilitate writing and reading encrypted records to S3.&lt;/p&gt;
&lt;p&gt;When the encrypted data key (EDK) is stored in an &amp;#34;Instruction File&amp;#34; instead of S3&amp;#39;s metadata record, the EDK is exposed to an &amp;#34;Invisible Salamanders&amp;#34; attack  (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;### Background - Key Commitment&lt;/p&gt;
&lt;p&gt;There is a cryptographic property whereby under certain conditions, a single ciphertext can be decrypted into 2 different plaintexts by using different encryption keys. To address this issue, strong encryption schemes use what is known as &amp;#34;key commitment&amp;#34;, a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message.&lt;/p&gt;
&lt;p&gt;In older versions of S3EC, when customers are also using a feature called &amp;#34;Instruction File&amp;#34; to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object.  For such customers an attack that leverages the lack of key commitment is possible. A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C. Any future attem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x8cp-jf6f-r4xh</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-14761</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-14761</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: aws-sdk-for-php&lt;/p&gt;
&lt;p&gt;Missing cryptographic key commitment in the AWS SDK for PHP may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an &amp;#34;instruction file&amp;#34; instead of S3&amp;#39;s metadata record. To mitigate this issue, upgrade AWS SDK for PHP to version 3.368.0 or later&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: aws-sdk-for-php&lt;/p&gt;
&lt;p&gt;Missing cryptographic key commitment in the AWS SDK for PHP may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an &amp;#34;instruction file&amp;#34; instead of S3&amp;#39;s metadata record. To mitigate this issue, upgrade AWS SDK for PHP to version 3.368.0 or later&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-14761</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0151 — TYPO3 Extension: Mehrere Schwachstellen ermöglichen Manipulation von Dateien</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0151</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in TYPO3 Extension ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in TYPO3 Extension ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0151</guid>
    </item>
  </channel>
</rss>
