<?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-08T15:07:35.297158+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/cve-2026-0636</id>
    <title>CVE-2026-0636 — LDAP Injection Vulnerability in LDAPStoreHelper.java</title>
    <updated>2026-10-08T15:07:35.466984+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Legion of the Bouncy Castle Inc. BC-JAVA, Red Hat AMQ Broker 7.12.7, Red Hat AMQ Broker 7.13.5, Red Hat AMQ Broker 7.14.1, Red Hat Build of Apache Camel 4.14 for Quarkus 3.27, Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14, Red Hat build of Quarkus 3.20.6.SP1, Red Hat build of Quarkus 3.27.3.SP1, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7, Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8 and 35 more</p>
<p>Improper neutralization of special elements used in an LDAP query ('LDAP injection') vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (prov modules).</p>
<p>This vulnerability is associated with program files LDAPStoreHelper.</p>
<p>This issue affects BC-JAVA: from 1.74 before 1.80.2, from 1.81 before 1.81.1, from 1.82 before 1.84.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-0636"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3g76-f9xq-8vp6</id>
    <title>GHSA-3g76-f9xq-8vp6 — Vert.x has a DoS via unbounded server-side SNI SslContext cache growth</title>
    <updated>2026-10-08T15:07:35.467172+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: io.vertx:vertx-core</p>
<p>Potential unbounded server-side SNI `SslContext` cache growth in Vert.x TLS handling, with = resource-exhaustion / DoS impact. On affected versions, matching server-side SNI names are cached via `computeIfAbsent(serverName, ...)` in a serverName-keyed `SslContext` cache.</p>
<p>The implementation differs slightly by branch, but the same sink appears to be present in released versions `4.3.4` through `5.0.11`:
- `4.3.x`: `SSLHelper`
- `4.4.x` / `4.5.x`: `SslChannelProvider`
- `5.0.x` and current `master`: `SslContextProvider`</p>
<p>When server-side SNI is enabled and wildcard or otherwise broad hostname mappings are used, an unauthenticated client can send many distinct matching SNI names and cause the server to retain increasing numbers of `SslContext` entries over time, leading to increasing memory consumption and possible DoS conditions.</p>
<p>## Steps to reproduce</p>
<p>1. Configure a Vert.x server with `setSsl(true)` and `setSni(true)`.
2. Use a keystore or mapping where many distinct SNI names match a wildcard or similarly broad rule.
3. Send repeated connections with distinct matching SNI values.
4. Observe that the SNI cache size grows with the number of unique matching names.</p>
<p>## What are the affected versions?</p>
<p>Affected released versions confirmed on `origin`:
- `4.3.4` through `4.3.8`
- `4.4.0` through `4.4.9`
- `4.5.0` through `4.5.26`
- `5.0.0` through `5.0.11`</p>
<p>Not affected by the same sink:
- `4.0.x` through `4.2.x`
- `4.3.0` through `4.3.3`</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3g76-f9xq-8vp6"/>
  </entry>
</feed>
