<?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://vulnerability.circl.lu</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 15:38:03 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-82358</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-82358</link>
      <description>&lt;p&gt;RT-Labs AB C-Open CANopen contains a write protection bypass in the SDO (Service Data Object) server implementation &amp;#39;src/co_sdo_server.c&amp;#39; that fails to properly validate write permissions when processing download-segment frames. An unauthenticated attacker on the CAN bus can initiate an SDO upload for a read-only Object Dictionary (OD) entry, which sets a data pointer to the read-only object, then send download-segment frames to write to that memory location. The download-segment handler does not verify that a download session is active, allowing any CANopen node to overwrite read-only OD entries using two SDO frames. Note that CANopen protocol operates over CAN bus and does not provide built-in authentication mechanisms. Fixed in 1.1.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RT-Labs AB C-Open CANopen contains a write protection bypass in the SDO (Service Data Object) server implementation &amp;#39;src/co_sdo_server.c&amp;#39; that fails to properly validate write permissions when processing download-segment frames. An unauthenticated attacker on the CAN bus can initiate an SDO upload for a read-only Object Dictionary (OD) entry, which sets a data pointer to the read-only object, then send download-segment frames to write to that memory location. The download-segment handler does not verify that a download session is active, allowing any CANopen node to overwrite read-only OD entries using two SDO frames. Note that CANopen protocol operates over CAN bus and does not provide built-in authentication mechanisms. Fixed in 1.1.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-82358</guid>
    </item>
    <item>
      <title>GHSA-grg4-frf9-pvw5</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-grg4-frf9-pvw5</link>
      <description>&lt;p&gt;RT-Labs AB C-Open CANopen contains a write protection bypass in the SDO (Service Data Object) server implementation &amp;#39;src/co_sdo_server.c&amp;#39; that fails to properly validate write permissions when processing download-segment frames. An unauthenticated attacker on the CAN bus can initiate an SDO upload for a read-only Object Dictionary (OD) entry, which sets a data pointer to the read-only object, then send download-segment frames to write to that memory location. The download-segment handler does not verify that a download session is active, allowing any CANopen node to overwrite read-only OD entries using two SDO frames. Note that CANopen protocol operates over CAN bus and does not provide built-in authentication mechanisms. Fixed in 1.1.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RT-Labs AB C-Open CANopen contains a write protection bypass in the SDO (Service Data Object) server implementation &amp;#39;src/co_sdo_server.c&amp;#39; that fails to properly validate write permissions when processing download-segment frames. An unauthenticated attacker on the CAN bus can initiate an SDO upload for a read-only Object Dictionary (OD) entry, which sets a data pointer to the read-only object, then send download-segment frames to write to that memory location. The download-segment handler does not verify that a download session is active, allowing any CANopen node to overwrite read-only OD entries using two SDO frames. Note that CANopen protocol operates over CAN bus and does not provide built-in authentication mechanisms. Fixed in 1.1.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-grg4-frf9-pvw5</guid>
    </item>
  </channel>
</rss>
