<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T08:52:35.613134+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/bdu:2023-04236</id>
    <title>bdu:2023-04236</title>
    <updated>2026-10-02T08:52:35.615492+00:00</updated>
    <content>bdu:2023-04236</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2023-04236"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-3825</id>
    <title>CVE-2023-3825</title>
    <updated>2026-10-02T08:52:35.615564+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PTC KEPServerEX</p>
<p>PTC’s KEPServerEX Versions 6.0 to 6.14.263 are vulnerable to being made to read a recursively defined object that leads to uncontrolled resource consumption. KEPServerEX uses OPC UA, a protocol which defines various object types that can be nested to create complex arrays. It does not implement a check to see if such an object is recursively defined, so an attack could send a maliciously created message that the decoder would try to decode until the stack overflowed and the device crashed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-3825"/>
  </entry>
</feed>
