<?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-17T15:59:43.716461+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-109143</id>
    <title>EUVD-2026-109143</title>
    <updated>2026-10-17T15:59:43.776918+00:00</updated>
    <content>EUVD-2026-109143</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-109143"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2013-7293</id>
    <title>fkie_cve-2013-7293</title>
    <updated>2026-10-17T15:59:43.776967+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The ASUS WL-330NUL router has a configuration process that relies on accessing the 192.168.1.1 IP address, but the documentation advises users to instead access a DNS hostname that does not always resolve to 192.168.1.1, which makes it easier for remote attackers to hijack the configuration traffic by controlling the server associated with that hostname.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2013-7293"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6xxp-p3pp-qrxg</id>
    <title>GHSA-6xxp-p3pp-qrxg</title>
    <updated>2026-10-17T15:59:43.776998+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The ASUS WL-330NUL router has a configuration process that relies on accessing the 192.168.1.1 IP address, but the documentation advises users to instead access a DNS hostname that does not always resolve to 192.168.1.1, which makes it easier for remote attackers to hijack the configuration traffic by controlling the server associated with that hostname.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6xxp-p3pp-qrxg"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2013-7293</id>
    <title>gsd-2013-7293</title>
    <updated>2026-10-17T15:59:43.777015+00:00</updated>
    <content>gsd-2013-7293</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2013-7293"/>
  </entry>
</feed>
