<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/csaf_bendergmbhcokg/10</id>
  <title>Most recent entries from csaf_bendergmbhcokg</title>
  <updated>2026-10-02T07:10:25.336775+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/vde-2025-084</id>
    <title>VDE-2025-084 — Bender Charge Controller Vulnerability - Unsecure Communication</title>
    <updated>2025-09-08T07:00:00+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Bender is publishing this advisory to inform customers about a security vulnerability in the Charge Controller product families. Bender has analyzed the weakness and determined that the electrical safety of the devices is not affected. Bender considers the weakness to be of high risk and it should be patched immediately.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/vde-2025-084"/>
    <published>2025-09-08T07:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/vde-2025-061</id>
    <title>VDE-2025-061 — Bender Charge Controller Vulnerability - Disclosure Of Stored Credentials When Authenticated</title>
    <updated>2025-09-08T07:00:00+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Bender is publishing this advisory to inform customers about a security vulnerability in the Charge Controller product families. Bender has analyzed the weakness and determined that the electrical safety of the devices is not affected. Bender considers the weakness to be of high risk and it should be patched immediately.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/vde-2025-061"/>
    <published>2025-09-08T07:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/vde-2021-047</id>
    <title>VDE-2021-047 — Bender/ebee: Multiple Charge Controller Vulnerabilities</title>
    <updated>2022-04-26T10:00:00+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Bender is publishing this advisory to inform customers about multiple security vulnerabilities in the Charge Controller product families.Bender has analysed the weaknesses and determined that the electrical safety of the devices is not concerned. To Benders knowledge, proof-of-concept code or exploits for the weaknesses are not available to the public.Bender considers some weaknesses to be critical and thus need to be patched immediately. Therefore, patches are provided as maintenance branch versions 5.11.2, 5.12.5, 5.13.2 and 5.20.2. Future software releases will of course already include these patches.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/vde-2021-047"/>
    <published>2022-04-26T10:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/vde-2020-043</id>
    <title>VDE-2020-043 — Bender: COMTRAXX &lt; 4.2.0 affected by inadquate credentials check vulnerability</title>
    <updated>2020-10-16T06:54:00+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Bender is publishing this advisory to inform customers about a security vulnerability in all devices running the COMTRAXX software.</p>
<p>The user authorization is validated for most, but not all routes in the system. A user with knowledge about the routes can read and write configuration data without prior authorization.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/vde-2020-043"/>
    <published>2020-10-16T06:54:00+00:00</published>
  </entry>
</feed>
