<?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-03T07:09:17.712324+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/cve-2026-24281</id>
    <title>CVE-2026-24281 — Apache ZooKeeper: Reverse-DNS fallback enables hostname verification bypass in ZooKeeper ZKTrustManager</title>
    <updated>2026-10-03T07:09:18.619042+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Apache Software Foundation Apache ZooKeeper, Red Hat AMQ Broker 7.12.7, Red Hat AMQ Broker 7.13.5, Red Hat AMQ Broker 7.14.0, Red Hat Streams for Apache Kafka 2.9.4, Red Hat OpenShift AI 2.25, Red Hat build of Apache Camel for Spring Boot 4, Red Hat build of Debezium 2, Red Hat build of Debezium 3, Red Hat Data Grid 8 and 7 more</p>
<p>Hostname verification in Apache ZooKeeper ZKTrustManager falls back to reverse DNS (PTR) when IP SAN validation fails, allowing attackers who control or spoof PTR records to impersonate ZooKeeper servers or clients with a valid certificate for the PTR name. It's important to note that attacker must present a certificate which is trusted by ZKTrustManager which makes the attack vector harder to exploit. Users are recommended to upgrade to version 3.8.6 or 3.9.5, which fixes this issue by introducing a new configuration option to disable reverse DNS lookup in client and quorum protocols.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-24281"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-3qp7-7mw8-wx86</id>
    <title>GHSA-3qp7-7mw8-wx86 — Netty has an IPv6 Subnet Filter Bypass via Incorrect Comparator Masking</title>
    <updated>2026-10-03T07:09:18.619282+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: io.netty:netty-handler</p>
<p>### Summary
An attacker can bypass IPv6 subnet rules due to an incorrect masking operation in IpSubnetFilterRule.compareTo(). Valid public IP addresses can bypass the restrictions.</p>
<p>### Details
`io.netty.handler.ipfilter.IpSubnetFilterRule#compareTo(java.net.InetSocketAddress)` method performs a bitwise AND between the incoming IP address and the configured networkAddress, instead of the subnetMask.</p>
<p>### Impact
Access Control Bypass. Attacker can bypass IpSubnetFilter IPv6 access controls.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-3qp7-7mw8-wx86"/>
  </entry>
</feed>
