<?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/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-13T06:22:59.838576+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/euvd-2026-195517</id>
    <title>EUVD-2026-195517</title>
    <updated>2026-10-13T06:22:59.841063+00:00</updated>
    <content>EUVD-2026-195517</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-195517"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-48911</id>
    <title>fkie_cve-2024-48911</title>
    <updated>2026-10-13T06:22:59.841089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenCanary, a multi-protocol network honeypot, directly executed commands taken from its config file. Prior to version 0.9.4, where the config file is stored in an unprivileged user directory but the daemon is executed by root, it’s possible for the unprivileged user to change the config file and escalate permissions when root later runs the daemon. Version 0.9.4 contains a fix for the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-48911"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pf5v-pqfv-x8jj</id>
    <title>GHSA-pf5v-pqfv-x8jj — OpenCanary Executes Commands From Potentially Writable Config File</title>
    <updated>2026-10-13T06:22:59.841121+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: OpenCanary</p>
<p>### Impact</p>
<p>OpenCanary directly executed commands taken from its config file. Where the config file is stored in an unprivileged user directory but the daemon is executed by root, it’s possible for the unprivileged user to change the config file and escalate permissions when root later runs the daemon.</p>
<p>Thanks to the folks at [Whirlylabs](https://whirlylabs.com/) for finding and fixing this.</p>
<p>### Patches</p>
<p>Upgrade to 0.9.4 or higher.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pf5v-pqfv-x8jj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2024-248</id>
    <title>PYSEC-2024-248</title>
    <updated>2026-10-13T06:22:59.841152+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: opencanary</p>
<p>OpenCanary, a multi-protocol network honeypot, directly executed commands taken from its config file. Prior to version 0.9.4, where the config file is stored in an unprivileged user directory but the daemon is executed by root, it’s possible for the unprivileged user to change the config file and escalate permissions when root later runs the daemon. Version 0.9.4 contains a fix for the issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2024-248"/>
  </entry>
</feed>
