<?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://cve.radiocsirt.org</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>Sun, 18 Oct 2026 09:16:52 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0174 — De multiples vulnérabilités ont été découvertes dans LibreNMS. Elles permettent à un attaquant de provoquer une injecti…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0174</link>
      <description>certfr-2026-avi-0174</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0174</guid>
    </item>
    <item>
      <title>EUVD-2026-268921</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-268921</link>
      <description>EUVD-2026-268921</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-268921</guid>
    </item>
    <item>
      <title>fkie_cve-2026-26988</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-26988</link>
      <description>&lt;p&gt;LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring tool. Versions 25.12.0 and below contain an SQL Injection vulnerability in the ajax_table.php endpoint. The application fails to properly sanitize or parameterize user input when processing IPv6 address searches. Specifically, the address parameter is split into an address and a prefix, and the prefix portion is directly concatenated into the SQL query string without validation. This allows an attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access or database manipulation. This issue has been fixed in version 26.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;LibreNMS is an auto-discovering PHP/MySQL/SNMP based network monitoring tool. Versions 25.12.0 and below contain an SQL Injection vulnerability in the ajax_table.php endpoint. The application fails to properly sanitize or parameterize user input when processing IPv6 address searches. Specifically, the address parameter is split into an address and a prefix, and the prefix portion is directly concatenated into the SQL query string without validation. This allows an attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access or database manipulation. This issue has been fixed in version 26.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-26988</guid>
    </item>
    <item>
      <title>GHSA-h3rv-q4rq-pqcv — LibreNMS: SQL Injection in ajax_table.php spreads through a covert data stream.</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h3rv-q4rq-pqcv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: librenms/librenms&lt;/p&gt;
&lt;p&gt;### Summary
*SQL Injection in IPv6 Address Search functionality via `address` parameter**&lt;/p&gt;
&lt;p&gt;A SQL injection vulnerability exists in the `ajax_table.php` endpoint. The application fails to properly sanitize or parameterize user input when processing IPv6 address searches. Specifically, the `address` parameter is split into an address and a prefix, and the prefix portion is directly concatenated into the SQL query string without validation. This allows an attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access or database manipulation.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is located in the logic that handles address searching when `search_type` is set to `ipv6`.&lt;/p&gt;
&lt;p&gt;The application takes the user-supplied `address` parameter and splits it using the `/` delimiter:
```PHP
[$address, $prefix] = explode(&amp;#39;/&amp;#39;, $vars[&amp;#39;address&amp;#39;]);
```
If the search_type is ipv6 and the $prefix variable is not empty, the code constructs the SQL query by directly concatenating the $prefix variable into the string:
```
} elseif ($vars[&amp;#39;search_type&amp;#39;] == &amp;#39;ipv6&amp;#39;) {
    // ... code omitted ...
    if (! empty($prefix)) {
        // VULNERABILITY: Direct concatenation of user input
        $sql .= &amp;#34; AND ipv6_prefixlen = &amp;#39;$prefix&amp;#39;&amp;#34;;
    }
}
```
Unlike the ipv4 block, which attempts to use prepared statements (binding parameters via $param[]), the ipv6 block treats the prefix as a raw string. By supplying an input containing a /, an attacker can populate the $prefix variable. If this va…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: librenms/librenms&lt;/p&gt;
&lt;p&gt;### Summary
*SQL Injection in IPv6 Address Search functionality via `address` parameter**&lt;/p&gt;
&lt;p&gt;A SQL injection vulnerability exists in the `ajax_table.php` endpoint. The application fails to properly sanitize or parameterize user input when processing IPv6 address searches. Specifically, the `address` parameter is split into an address and a prefix, and the prefix portion is directly concatenated into the SQL query string without validation. This allows an attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access or database manipulation.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is located in the logic that handles address searching when `search_type` is set to `ipv6`.&lt;/p&gt;
&lt;p&gt;The application takes the user-supplied `address` parameter and splits it using the `/` delimiter:
```PHP
[$address, $prefix] = explode(&amp;#39;/&amp;#39;, $vars[&amp;#39;address&amp;#39;]);
```
If the search_type is ipv6 and the $prefix variable is not empty, the code constructs the SQL query by directly concatenating the $prefix variable into the string:
```
} elseif ($vars[&amp;#39;search_type&amp;#39;] == &amp;#39;ipv6&amp;#39;) {
    // ... code omitted ...
    if (! empty($prefix)) {
        // VULNERABILITY: Direct concatenation of user input
        $sql .= &amp;#34; AND ipv6_prefixlen = &amp;#39;$prefix&amp;#39;&amp;#34;;
    }
}
```
Unlike the ipv4 block, which attempts to use prepared statements (binding parameters via $param[]), the ipv6 block treats the prefix as a raw string. By supplying an input containing a /, an attacker can populate the $prefix variable. If this va…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h3rv-q4rq-pqcv</guid>
    </item>
  </channel>
</rss>
