You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by gi...@apache.org on 2026/08/11 15:07:21 UTC
(solr-site) branch asf-staging updated: Commit build products
This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/solr-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new ca789a8aa Commit build products
ca789a8aa is described below
commit ca789a8aa7b84944cb79d1e9165db18016fe24fd
Author: Build Pelican (action) <pr...@infra.apache.org>
AuthorDate: Tue Aug 11 15:07:15 2026 +0000
Commit build products
---
output/feeds/all.atom.xml | 333 +++++++++++++--
output/feeds/solr/vex.atom.xml | 330 +++++++++++++--
output/security-dependency-cves.html | 161 ++++++-
output/solr.openvex.json | 632 +++++++++++++++++++++++++++-
output/solr.vex.json | 793 ++++++++++++++++++++++++++++++-----
output/vex.html | 610 +++++++++++++++++++++++++--
6 files changed, 2646 insertions(+), 213 deletions(-)
diff --git a/output/feeds/all.atom.xml b/output/feeds/all.atom.xml
index 9c7f15b26..1900061cc 100644
--- a/output/feeds/all.atom.xml
+++ b/output/feeds/all.atom.xml
@@ -1,5 +1,252 @@
<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr</title><link href="/" rel="alternate"/><link href="/feeds/all.atom.xml" rel="self"/><id>/</id><updated>2026-07-18T00:00:00+00:00</updated><entry><title>Apache Commons BeanUtils: class-loader access via a 'declaredClass' property path</title><link href="/cve-2025-48734.html" rel="alternate"/><published>2026-07-18T00:00:00+00:00</published><updated>2026-07-18T00:00:00+00:00</updated><author><name>Solr Developers</name></author><i [...]
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr</title><link href="/" rel="alternate"/><link href="/feeds/all.atom.xml" rel="self"/><id>/</id><updated>2026-07-31T00:00:00+00:00</updated><entry><title>Apache Avro (Java): RCE reading a crafted schema / DoS deserializing untrusted data</title><link href="/cve-2024-47561.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author> [...]
+an attacker-controlled Avro <strong>schema</strong> can instantiate arbitrary classes (affects avro &lt; 1.11.4).
+CVE-2023-39410 is a memory-exhaustion / DoS issue when <strong>deserializing untrusted Avro data</strong> (affects
+avro &lt; 1.11.3). Both require the application to feed attacker-controlled Avro …</p></summary><content type="html"><p>CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing
+an attacker-controlled Avro <strong>schema</strong> can instantiate arbitrary classes (affects avro &lt; 1.11.4).
+CVE-2023-39410 is a memory-exhaustion / DoS issue when <strong>deserializing untrusted Avro data</strong> (affects
+avro &lt; 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>Solr does not use Apache Avro.</strong> There is no <code>org.apache.avro</code> usage anywhere in the Solr
+ codebase, and Solr ships no standalone <code>avro-*.jar</code>. Avro appears only as an embedded/transitive
+ artifact of the optional Hadoop integration (the <code>hdfs</code> / <code>hadoop-auth</code> modules, which are not part
+ of a default install).</li>
+<li><strong>The vulnerable entry points are never reached.</strong> Solr never parses an externally-supplied Avro
+ schema and never deserializes untrusted Avro data — the only code that pulls Avro in is Hadoop's
+ own internal machinery, driven by administrator-supplied configuration, not by untrusted request
+ input.</li>
+</ul>
+<p>The affected range covers the 9.x line, where the optional Hadoop modules transitively carry Avro
+1.9.2; Solr's own code path never invokes it.</p></content><category term="solr/vex"/></entry><entry><title>jackson-core: memory disclosure via source snippet in JsonLocation error messages</title><link href="/cve-2025-49128.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-49128.html</id><summary type="html"><p>CVE-2025-49128 can dis [...]
+includes in <code>JsonLocation</code> (e.g. surfaced in parse-error messages). It affects jackson-core &lt; 2.13.0.</p>
+<p>Solr is <strong>not affected</strong>. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 — both …</p></summary><content type="html"><p>CVE-2025-49128 can disclose adjacent buffer memory through the source snippet that jackson-core
+includes in <code>JsonLocation</code> (e.g. surfaced in parse-error messages). It affects jackson-core &lt; 2.13.0.</p>
+<p>Solr is <strong>not affected</strong>. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 — both
+well past the 2.13.0 fix. The <code>2.12.7</code> copy a scanner flags is Hadoop's shaded jackson-core,
+reachable only via the optional Hadoop modules, which parse administrator-supplied configuration
+rather than untrusted external JSON, and whose parse errors are not returned to remote clients.</p></content><category term="solr/vex"/></entry><entry><title>jackson-core: async-parser number-length bypass and deep-nesting StackOverflow (DoS)</title><link href="/cve-2025-52999.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-52999.html</id [...]
+(an incomplete fix for GHSA-72hv-8253-57qq; affects &lt; 2.18.8 and 2.19.0–2.21.3). CVE-2025-52999 is a
+<code>StackOverflowError</code> when parsing <strong>very deeply nested</strong> input (affects &lt; 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The async parser is never used …</strong></li></ul></summary><content type="html"><p>GHSA-r7wm-3cxj-wff9 is a <code>maxNumberLength</code> bypass in jackson-core's <strong>async / non-blocking</strong> parser
+(an incomplete fix for GHSA-72hv-8253-57qq; affects &lt; 2.18.8 and 2.19.0–2.21.3). CVE-2025-52999 is a
+<code>StackOverflowError</code> when parsing <strong>very deeply nested</strong> input (affects &lt; 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The async parser is never used.</strong> Solr deserializes JSON with the standard <em>synchronous</em> Jackson
+ parser; it never calls the non-blocking <code>NonBlockingByteArrayParser</code> API, so the async-only
+ <code>maxNumberLength</code> bypass (GHSA-r7wm) is unreachable — as already assessed for GHSA-72hv-8253-57qq.</li>
+<li><strong>Solr's own jackson-core is patched.</strong> The bundled jackson-core is 2.18.0 in current 9.x and
+ 2.22.0 in 9.11 — both fixed for the deep-nesting StackOverflow (fixed in 2.15.0). The <code>2.12.7</code>
+ copy a scanner flags is Hadoop's <strong>shaded</strong> jackson, reachable only through the optional Hadoop
+ modules, which parse administrator-supplied configuration rather than untrusted external JSON.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>Nimbus JOSE + JWT: uncontrolled recursion (DoS) parsing crafted JOSE objects</title><link href="/cve-2025-53864.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-53864.html</id><summary type="html"><p>CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Ni [...]
+parsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x &lt; 9.37.4 and 10.0.x &lt; 10.0.2).</p>
+<p>Solr is <strong>not affected</strong>. Solr's JWT authentication (the optional <code>jwt-auth</code> module, <code>JWTAuthPlugin</code>)
+parses and validates tokens exclusively …</p></summary><content type="html"><p>CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Nimbus JOSE + JWT library when
+parsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x &lt; 9.37.4 and 10.0.x &lt; 10.0.2).</p>
+<p>Solr is <strong>not affected</strong>. Solr's JWT authentication (the optional <code>jwt-auth</code> module, <code>JWTAuthPlugin</code>)
+parses and validates tokens exclusively with <strong>jose4j</strong> (<code>org.jose4j.*</code> — the plugin imports jose4j
+and does not reference <code>com.nimbusds</code> at all). Nimbus JOSE + JWT is not on Solr's JWT-processing code
+path; it appears only as a transitive/declared reference and is never invoked to parse an incoming
+token, so the vulnerable recursive parser cannot be reached by an attacker-supplied JWT.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: Digest authentication lossy encoding</title><link href="/cve-2026-10050.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-10050.html</id><summary type="html"><p>CVE-2026- [...]
+(in <code>jetty-security</code>), which can weaken Digest credential handling. It affects the Jetty branches
+Solr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12 …</p></summary><content type="html"><p>CVE-2026-10050 is a lossy-encoding flaw in Eclipse Jetty's <strong>Digest authentication</strong> implementation
+(in <code>jetty-security</code>), which can weaken Digest credential handling. It affects the Jetty branches
+Solr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12.1.10).</p>
+<p>Solr is <strong>not affected</strong>. Solr bundles <code>jetty-security</code> as part of the Jetty server stack, but it
+does not use Jetty's declarative security: it never installs a Jetty <code>SecurityHandler</code> /
+<code>ConstraintSecurityHandler</code> and never configures a Jetty <code>Authenticator</code> (Digest or otherwise). Solr
+authenticates requests in its own servlet filter (<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code>
+framework — Basic, JWT, Kerberos, PKI, etc.), so Jetty's Digest-authentication code path — the code
+this CVE affects — is never invoked. The affected range spans the releases whose bundled Jetty is in
+an affected branch (Solr 7.3.0 – 10.0.0).</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: HTTP/1.1 request trailers leak across keep-alive requests</title><link href="/cve-2026-10051.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-10051.html</id><summary type="html"><p>CVE-2026-10051 is an information-ex [...]
+not reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request
+can be observed via <code>getTrailers()</code> on a later request on the same connection. It has security impact
+only for applications that …</p></summary><content type="html"><p>CVE-2026-10051 is an information-exposure bug in Jetty's <code>HttpConnection</code>: the <code>_trailers</code> field is
+not reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request
+can be observed via <code>getTrailers()</code> on a later request on the same connection. It has security impact
+only for applications that <strong>read HTTP trailers</strong> (<code>request.getTrailers()</code>) and use them for logic or
+security decisions.</p>
+<p>Solr is <strong>not affected</strong>. Solr does not read HTTP request trailers anywhere — there is no
+<code>getTrailers()</code> / trailer-field usage in the Solr codebase — so stale trailer state on a pooled
+connection is never observed by Solr and cannot influence request handling or authorization. The
+affected range spans the releases whose bundled Jetty is in an affected branch (Solr 7.3.0 – 10.0.0).</p></content><category term="solr/vex"/></entry><entry><title>Apache Thrift (Java): TLS hostname verification in TSSLTransportFactory</title><link href="/cve-2026-43869.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-43869.html</id><summa [...]
+<code>TSSLTransportFactory</code> (affects libthrift ≤ 0.22.0, fixed in 0.23.0): a client using Thrift's TLS
+transport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on
+that connection.</p>
+<p>Solr is <strong>not affected</strong> in any default or recommended configuration …</p></summary><content type="html"><p>CVE-2026-43869 is a TLS hostname-verification weakness in Apache Thrift's
+<code>TSSLTransportFactory</code> (affects libthrift ≤ 0.22.0, fixed in 0.23.0): a client using Thrift's TLS
+transport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on
+that connection.</p>
+<p>Solr is <strong>not affected</strong> in any default or recommended configuration. <code>libthrift</code> is bundled only by
+the optional, opt-in <strong><code>jaegertracer-configurator</code></strong> module (Jaeger distributed-tracing exporter) —
+it is not part of a default Solr install, and Solr does not use Thrift's TLS transport anywhere else.
+Even when Jaeger tracing is enabled, Solr exports spans to an <strong>operator-configured</strong> Jaeger backend
+(a trusted, first-party collector), not to an untrusted remote host, so there is no untrusted TLS
+peer for the missing hostname check to expose. The issue is only relevant to an operator who both
+enables Jaeger tracing and deliberately points it at an untrusted TLS endpoint.</p></content><category term="solr/vex"/></entry><entry><title>Apache Commons Configuration: StackOverflowError for YAML input with cycles</title><link href="/cve-2026-45205.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-45205.html</id><summary type="html">< [...]
+containing reference cycles (affects 2.2 – 2.14.x, fixed in 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>. Solr uses <code>commons-configuration2</code> only transitively, via the optional
+Hadoop integration (Kerberos / HDFS support), to load <strong>administrator-supplied</strong> Hadoop configuration
+files — not …</p></summary><content type="html"><p>CVE-2026-45205 is a <code>StackOverflowError</code> (DoS) when Apache Commons Configuration parses YAML input
+containing reference cycles (affects 2.2 – 2.14.x, fixed in 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>. Solr uses <code>commons-configuration2</code> only transitively, via the optional
+Hadoop integration (Kerberos / HDFS support), to load <strong>administrator-supplied</strong> Hadoop configuration
+files — not untrusted, externally-supplied YAML. No Solr request path feeds attacker-controlled YAML
+to Commons Configuration, so the cyclic-YAML parser cannot be driven by an adversary. (This matches
+the existing assessment of the other Commons Configuration CVEs in Solr.)</p></content><category term="solr/vex"/></entry><entry><title>Apache Calcite: arbitrary class loading via a user-controlled model</title><link href="/cve-2026-46718.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-46718.html</id><summary type="html"><p>CVE-2026 [...]
+execution (affects calcite-core 1.5.0 – 1.41.x, fixed in 1.42.0). Exploitation requires the
+application to let an attacker supply the Calcite <em>model</em> (the JSON schema/model definition that can
+name factory classes).</p>
+<p>Solr is …</p></summary><content type="html"><p>CVE-2026-46718 lets a <strong>user-controlled Calcite model</strong> load arbitrary classes, leading to code
+execution (affects calcite-core 1.5.0 – 1.41.x, fixed in 1.42.0). Exploitation requires the
+application to let an attacker supply the Calcite <em>model</em> (the JSON schema/model definition that can
+name factory classes).</p>
+<p>Solr is <strong>not affected</strong>. Calcite is used only by the optional <code>sql</code> module (Parallel SQL, the <code>/sql</code>
+handler). Solr constructs the Calcite schema/model <strong>server-side</strong> from the target collection; users
+submit only a SQL statement, never a Calcite model or schema-factory definition. There is no request
+path through which an attacker can supply a Calcite model, so the arbitrary-class-loading vector is
+never reached.</p></content><category term="solr/vex"/></entry><entry><title>jackson-databind: nested-toString DoS, InetSocketAddress SSRF, and deserialization-filter bypasses</title><link href="/cve-2026-50193.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-50193.html</id><summary type="html"><p>Four jackson-databind issues, in two [...]
+<ul>
+<li><strong>Only the Hadoop-shaded old copy is affected.</strong> CVE-2026-50193 (StackOverflow on <code>toString()</code> of a
+ deeply-nested <code>JsonNode</code>, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when
+ deserializing into <code>InetSocketAddress</code>, fixed 2.18.8 / 2.21.4) do not affect Solr's own
+ jackson-databind (2.18 …</li></ul></summary><content type="html"><p>Four jackson-databind issues, in two groups:</p>
+<ul>
+<li><strong>Only the Hadoop-shaded old copy is affected.</strong> CVE-2026-50193 (StackOverflow on <code>toString()</code> of a
+ deeply-nested <code>JsonNode</code>, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when
+ deserializing into <code>InetSocketAddress</code>, fixed 2.18.8 / 2.21.4) do not affect Solr's own
+ jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 — both patched). The <code>2.12.7.1</code> a scanner
+ flags is Hadoop's shaded copy, reachable only through the optional Hadoop modules, which process
+ administrator-supplied configuration rather than untrusted external JSON.</li>
+<li><strong>Require Jackson features Solr does not use.</strong> CVE-2026-54515 (case-insensitive deserialization
+ bypassing per-property <code>@JsonIgnoreProperties</code>), CVE-2026-59889 (<code>@JsonView</code> bypass for
+ <code>@JsonUnwrapped</code> container properties), CVE-2026-59888 (<code>@JsonIgnore</code> on a Record property bypassed
+ via a <code>PropertyNamingStrategy</code>), and GHSA-mhm7-754m-9p8w (<code>@JsonView</code> bypass for creator properties
+ with <code>@JsonTypeInfo(include = As.EXTERNAL_PROPERTY)</code>) can reach Solr's own jackson-databind, but
+ only when an application relies on those annotation-based mechanisms — case-insensitive property
+ mapping, <code>@JsonView</code>, <code>@JsonUnwrapped</code>, <code>@JsonIgnore</code> on records, or <code>@JsonTypeInfo</code> external-property
+ polymorphism — to restrict which fields untrusted input may set. Solr uses none of them: it maps
+ request JSON to fixed, known types and never applies <code>@JsonView</code>/<code>@JsonIgnore</code>-based deserialization
+ filtering or polymorphic typing to untrusted input, so these bypasses have nothing to bypass.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>jackson-databind: PolymorphicTypeValidator allowlist bypasses (unsafe deserialization)</title><link href="/cve-2026-54512.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-54512.html</id><summary type="html"><p>CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-dat [...]
+generic type parameters (54512) and via an array-subtype allowlist gap in
+<code>allowIfSubType</code> (54513) — that can let unexpected classes be instantiated during polymorphic
+deserialization (affects 2.10.0–2.18.7 and 2.19.0–2.21.3).</p>
+<p>Solr is <strong>not affected …</strong></p></summary><content type="html"><p>CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's <code>PolymorphicTypeValidator</code> — via
+generic type parameters (54512) and via an array-subtype allowlist gap in
+<code>allowIfSubType</code> (54513) — that can let unexpected classes be instantiated during polymorphic
+deserialization (affects 2.10.0–2.18.7 and 2.19.0–2.21.3).</p>
+<p>Solr is <strong>not affected</strong>. Both issues are only exploitable when an application enables <strong>polymorphic
+deserialization</strong> — default typing (<code>activateDefaultTyping</code>), <code>@JsonTypeInfo</code>, or a
+<code>BasicPolymorphicTypeValidator</code> allowlist — and then deserializes attacker-controlled JSON through it.
+Solr does none of this: it maps request JSON to fixed, known target types and never enables default
+typing or polymorphic deserialization of untrusted input, so the <code>PolymorphicTypeValidator</code> code path
+these CVEs target is never exercised. (The <code>2.12.7.1</code> copy a scanner flags is Hadoop's shaded
+jackson-databind; Solr's own is 2.18.0 in current 9.x and 2.22.0 in 9.11.)</p></content><category term="solr/vex"/></entry><entry><title>JLine: unauthenticated remote DoS in the Telnet server</title><link href="/cve-2026-56740.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-56740.html</id><summary type="html"><p>CVE-2026-56740 and C [...]
+Telnet server</strong> — unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values
+(56741) in the <code>jline-remote-telnet</code> Telnet daemon (affects &lt; 3.30.14, and the 4.0.x / 4.1.x lines).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The vulnerable component is not shipped …</strong></li></ul></summary><content type="html"><p>CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in <strong>JLine's
+Telnet server</strong> — unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values
+(56741) in the <code>jline-remote-telnet</code> Telnet daemon (affects &lt; 3.30.14, and the 4.0.x / 4.1.x lines).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The vulnerable component is not shipped or run.</strong> Solr ships no <code>jline-remote-telnet</code> jar; the
+ <code>3.9.0</code> coordinate a scanner reports comes only from a dependency reference embedded in the bundled
+ <code>zookeeper-3.9.5</code> jar's metadata. Solr never starts a JLine Telnet server (<code>Telnetd</code>).</li>
+<li>JLine is used, at most, for the local interactive <code>bin/solr</code> CLI terminal — a <code>LineReader</code> on the
+ operator's own console, not a network-listening Telnet daemon — so nothing accepts remote Telnet
+ connections that the vulnerable NAWS/NEW-ENVIRON parsing could act on.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>Netty codec: SPDY / HTTP2-decompression / Bzip2 denial-of-service issues</title><link href="/cve-2026-56745.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-56745.html</id><summary type="html"><p>These five Netty issues are resource-exhaustion / DoS bugs in server- and d [...]
+(all affect Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 — the <strong>SPDY</strong> codec (<code>SpdyHttpDecoder</code> and SPDY
+ header/settings handling) in <code>netty-codec-http</code>.</li>
+<li>CVE-2026-56819 …</li></ul></summary><content type="html"><p>These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths
+(all affect Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 — the <strong>SPDY</strong> codec (<code>SpdyHttpDecoder</code> and SPDY
+ header/settings handling) in <code>netty-codec-http</code>.</li>
+<li>CVE-2026-56819 — server-side <strong>HTTP/2 decompression</strong> ByteBuf reference leak in <code>netty-codec-http2</code>.</li>
+<li>CVE-2026-59901 — infinite loop in the <strong>Bzip2</strong> decoder in <code>netty-codec-compression</code>.</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty acts strictly as a <strong>client</strong>. Solr's HTTP server is Jetty, not
+Netty: Solr never runs a Netty HTTP/HTTP2/SPDY server, never enables the SPDY codec, and never feeds
+attacker-controlled compressed (bzip2) streams through Netty. The vulnerable server/decoder code
+paths are therefore unreachable — the same reasoning as CVE-2026-33870 / CVE-2026-33871.</p></content><category term="solr/vex"/></entry><entry><title>Netty codec-http/http2: server-side HTTP handling issues (DoS, CORS/WebSocket, smuggling, CRLF)</title><link href="/cve-2026-59899.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-59899.html [...]
+Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-59899 — unbounded per-connection queue growth in <code>HttpContentEncoder</code> via HTTP/1.1
+ pipelining (server response encoding …</li></ul></summary><content type="html"><p>These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect
+Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-59899 — unbounded per-connection queue growth in <code>HttpContentEncoder</code> via HTTP/1.1
+ pipelining (server response encoding).</li>
+<li>CVE-2026-56746 — CORS short-circuit failure / security-control bypass (server CORS handler).</li>
+<li>CVE-2026-59898 — WebSocket V07/V08 handshaker missing Connection/Upgrade validation (server).</li>
+<li>CVE-2026-59921 — CRLF injection via multipart filename in the outbound <code>HttpPostRequestEncoder</code>.</li>
+<li>CVE-2026-59900 — Host-header de-duplication gap in HTTP/2→HTTP/1.x translation (server/proxy).</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty is used strictly as a <strong>client</strong>. Solr's HTTP server is Jetty:
+Solr never runs a Netty HTTP server, CORS handler, WebSocket server, or HTTP/2→1 proxy, and never
+uses Netty's multipart request encoder, so none of these code paths are reachable.</p></content><category term="solr/vex"/></entry><entry><title>lz4-java: out-of-bounds read via invalid arguments to native XXHash</title><link href="/cve-2026-59949.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-59949.html</id><summary type="html"><p> [...]
+JNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that
+passes an invalid array reference or an out-of-range <code>off</code>/<code>len</code> to the native XXHash methods can
+crash the JVM. It affects lz4-java …</p></summary><content type="html"><p>CVE-2026-59949 (CVSS 6.5) is an out-of-bounds read in the <code>at.yawk.lz4:lz4-java</code> codec: the
+JNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that
+passes an invalid array reference or an out-of-range <code>off</code>/<code>len</code> to the native XXHash methods can
+crash the JVM. It affects lz4-java ≤ 1.11.0 (fixed in 1.11.1). Exploitation requires an application
+to pass attacker-influenced array/offset/length values into those XXHash APIs.</p>
+<p>Solr is <strong>not affected</strong>. <code>lz4-java</code> is bundled only by the optional <code>cross-dc</code> module, where it is
+used by the embedded Apache Kafka client for LZ4 compression / checksums of cross-datacenter
+replication messages. Kafka calls the XXHash APIs with its own internally-managed, validated buffers
+and offsets — it does not forward attacker-controlled <code>off</code>/<code>len</code> values into the native methods —
+and the replication stream flows through an operator-controlled Kafka pipeline, not untrusted
+external input. The <code>cross-dc</code> module is not part of a default Solr installation, and no Solr request
+path reaches the vulnerable XXHash argument handling.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: HTTP/2 :authority vs Host header confusion</title><link href="/cve-2026-6790.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-6790.html</id><summary type="html"><p>CVE-2026-6790 is an input-validation gap [...]
+does not require the <code>:authority</code> pseudo-header to match the <code>Host</code> header, so a single request can
+carry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x
+through …</p></summary><content type="html"><p>CVE-2026-6790 is an input-validation gap in Jetty's HTTP/2 (and HTTP/3) request processing: Jetty
+does not require the <code>:authority</code> pseudo-header to match the <code>Host</code> header, so a single request can
+carry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x
+through 10.0.26, 12.0.x through 12.0.34). It has security impact only for applications that <strong>make
+security-sensitive decisions based on the request host</strong> — host-based access control, virtual-host
+isolation, multi-tenant routing, or host-derived redirect URLs.</p>
+<p>Solr is <strong>not affected</strong>. Solr does none of those things: it does not perform host-based access
+control or virtual-host/multi-tenant isolation, its authentication and authorization
+(<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code> framework) never key on the <code>Host</code>/<code>:authority</code>
+value, and it does not build security-sensitive redirects from the request host. With no
+host-dependent security decision, the host-confusion has no exploitable consequence in Solr.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: non-canonical URL paths in URIUtil.canonicalPath (authorization bypass)</title><link href="/cve-2026-8384.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-8384.html</id><s [...]
+path-parameter marker before dot-dot segments (e.g. <code>/public;/../admin/secret</code>) is not normalized,
+so a path-prefix authorization check can be bypassed. It is exploitable by applications that use
+Jetty's <code>SecurityHandler.PathMapped</code>, or that make an authorization decision on a …</p></summary><content type="html"><p>CVE-2026-8384 is a path-canonicalization flaw in Jetty's <code>URIUtil.canonicalPath()</code>: a semicolon
+path-parameter marker before dot-dot segments (e.g. <code>/public;/../admin/secret</code>) is not normalized,
+so a path-prefix authorization check can be bypassed. It is exploitable by applications that use
+Jetty's <code>SecurityHandler.PathMapped</code>, or that make an authorization decision on a canonicalized path
+at a <strong>different layer</strong> than the one that ultimately dispatches the request (the classic
+canonicalization <em>desync</em>).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>No desync between authorization and dispatch.</strong> <code>HttpSolrCall</code> computes the request path once
+ (<code>ServletUtils.getPathAfterContext()</code>), and uses that single value for <em>both</em> request routing
+ (<code>getPath()</code>) and authorization (<code>getAuthCtx()</code> builds its <code>AuthorizationContext</code> resource from the
+ same <code>getPath()</code>). <code>RuleBasedAuthorizationPlugin</code> therefore evaluates exactly the path that Solr
+ dispatches — there is no window in which authorization sees one path while a different path is
+ served, which is the precondition this CVE requires.</li>
+<li><strong>Path parameters are already stripped.</strong> Solr derives the path from <code>getServletPath()</code> +
+ <code>getPathInfo()</code>, which per the Servlet specification have path parameters (the <code>;…</code> segments this
+ bug abuses) removed by the container before Solr ever sees the path.</li>
+<li>Solr uses neither Jetty's <code>SecurityHandler.PathMapped</code> nor <code>URIUtil.canonicalPath()</code> directly.</li>
+</ul>
+<p>So even on an affected Jetty, the mis-canonicalization cannot produce an authorization bypass in
+Solr, because Solr's authorization and dispatch are driven by the same, single path value.</p></content><category term="solr/vex"/></entry><entry><title>Apache Commons BeanUtils: class-loader access via a 'declaredClass' property path</title><link href="/cve-2025-48734.html" rel="alternate"/><published>2026-07-18T00:00:00+00:00</published><updated>2026-07-18T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-18:/cve-2025-48734.html</id><summar [...]
<p>CVE-2025-48734 affects all Commons BeanUtils 1.x releases before 1.11.0. Solr has bundled
commons-beanutils since Solr 3.6.0, and every release that includes it, through Solr 10.0.0, ships an
affected 1.x version (1.7.0, then 1.8.3, 1.9.3 and 1.9.4 — all below 1.11.0). The affected range is
@@ -798,9 +1045,10 @@ who can supply a crafted dictionary file — either directly or embedded in a mo
OpenNLP deserializes — can therefore read local files from the server or trigger outbound requests
(server-side request forgery). Other OpenNLP XML parsing paths route through the hardened
<code>XmlUtil.createSaxParser()</code> helper, but this code path does not.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
-<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which parse dictionaries with secure
-XML processing that rejects DOCTYPE declarations and external entities.</p>
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed in OpenNLP 2.5.9 (and
+3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these parse dictionaries
+with secure XML processing that rejects DOCTYPE declarations and external entities.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable dictionary-parsing code path becomes reachable when:</p>
@@ -823,11 +1071,14 @@ archive passes through a single chokepoint before OpenNLP is allowed to deserial
to both standalone (filesystem configset) and SolrCloud (ZooKeeper) deployments, and whether the
dictionary is loaded by the <code>langid</code> / <code>analysis-extras</code> update processors or by the
schema-configured OpenNLP analyzers.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Arbitrary class instantiation via model manifest</title><link href="/cve-2026-42027.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve- [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Arbitrary class instantiation via model manifest</title><link href="/cve-2026-42027.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve-2026-42027.html</id><summary type="html"><p>CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue i [...]
<code>ExtensionLoader</code>. The <code>instantiateExtension(Class, String)</code> method loads a class named in a
model archive's <code>manifest.properties</code> via <code>Class.forName()</code> and only performs its
<code>isAssignableFrom</code> type check <em>after</em> the class has been loaded. Because <code>Class.forName()</code>
@@ -839,8 +1090,9 @@ runs the target class's static initializer at load time, an attacker who can sup
model archive can trigger the static initializer of any class on the classpath (e.g. one that
performs a JNDI lookup, outbound network I/O, or filesystem access), regardless of the
type check that follows.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively
-via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which consults a
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP
+2.5.9 (and 3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; the fix consults a
package-prefix allowlist <em>before</em> calling <code>Class.forName()</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
@@ -856,9 +1108,8 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>In Solr 9.11.0 the upstream allowlist defense is backfilled at the application layer, since the
-vulnerable jar cannot yet be upgraded (Solr must track the OpenNLP version used by
-<code>lucene-analysis-opennlp</code>). Every OpenNLP model is loaded as a resource through Solr's resource
+<p>As defense in depth, Solr 9.11 also validates OpenNLP models at the application layer before they
+reach <code>ExtensionLoader</code>. Every OpenNLP model is loaded as a resource through Solr's resource
loaders, so the archive is validated at that single chokepoint before OpenNLP is allowed to
deserialize it:</p>
<ul>
@@ -873,11 +1124,14 @@ deserialize it:</p>
</ul>
<p>Solr's own usage only ever references built-in <code>opennlp.*</code> factories, so legitimate models load
unchanged; only crafted models that try to instantiate arbitrary classes are blocked.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Out-of-memory denial of service via crafted model file</title><link href="/cve-2026-42440.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04 [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> is fixed — it upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the
+1.9.x backport) and adds the application-layer allowlist described above — and Solr <strong>10.1</strong> upgrades
+to 2.5.9. The affected (exploitable) range is therefore <strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 (plus Solr's
+own allowlist) closes this issue.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Out-of-memory denial of service via crafted model file</title><link href="/cve-2026-42440.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve-2026-42440.html</id><summary type="html"><p>CVE-2026-42440 (CVSS 7.5) is an out-of-memory [...]
model reader. The <code>AbstractModelReader</code> methods <code>getOutcomes()</code>, <code>getOutcomePatterns()</code> and
<code>getPredicates()</code> read a 32-bit signed integer count field from a binary model stream and pass it
directly to an array allocation without validating it. An attacker who can supply …</p></summary><content type="html"><p>CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary
@@ -888,9 +1142,9 @@ model file with a count set to <code>Integer.MAX_VALUE</code> trigge
model deserialization, before any substantial data is consumed.</p>
<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP 2.5.9 (and
-3.0.0-M3), and backported to the end-of-life 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these
-validate the count against an upper bound (default 10,000,000, configurable via the
-<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating.</p>
+3.0.0-M3), which validate the count against an upper bound (default 10,000,000, configurable via the
+<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating, and backported to the 1.9.x line as
+<code>opennlp-tools-1.9.5</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable model-loading code path becomes reachable when:</p>
@@ -907,12 +1161,14 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9. Solr has bundled OpenNLP (transitively,
-via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so every release from 7.3.0 through 10.0.0 ships an
-affected version (1.8.3 through 2.5.6). The affected range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fixed in Solr 9.11, which bundles the patched <code>opennlp-tools</code> 1.9.5, and in Solr 10.1, which upgrades
-the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9. Solr 10.0 remains affected (it ships
-OpenNLP 2.5.6).</p></content><category term="solr/vex"/></entry><entry><title>Apache Log4j Core: TLS hostname verification silently ignored in Socket, SMTP and Syslog appenders</title><link href="/cve-2026-34477.html" rel="alternate"/><published>2026-04-10T00:00:00+00:00</published><updated>2026-04-10T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-04-10:/cve-2026-34477.html</id><summary type="html"><p>CVE-2026-34477 is <strong>not [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p></content><category term="solr/vex"/></entry><entry><title>Apache Log4j Core: TLS hostname verification silently ignored in Socket, SMTP and Syslog appenders</title><link href="/cve-2026-34477.html" rel="alternate"/><published>2026-04-10T00:00:00+00:00</published><updated>2026-04-10T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-04-10:/cve-2026-34477.html</id><summary type="html"><p>CVE-2026-34477 is <strong>not [...]
Successful exploitation requires a specific, non-default logging configuration together with a privileged network position.
The following conditions <strong>must all be met</strong>:</p>
<ul>
@@ -1251,8 +1507,22 @@ so dependency scanners flag the <code>commons-lang3</code> JAR bundl
(<code>solr-hadoop-auth</code>) to load administrator-provided Hadoop configuration files. Class names are not
attacker-controlled in that path, so the recursion cannot be driven by an adversary and the
vulnerability is not exploitable in Solr.</p></content><category term="solr/vex"/></entry><entry><title>protobuf-java: Potential Denial of Service issue</title><link href="/cve-2024-7254.html" rel="alternate"/><published>2025-08-02T00:00:00+00:00</published><updated>2025-08-02T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2025-08-02:/cve-2024-7254.html</id><summary type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Ful [...]
-<p>CVE-2024-7254 affects all <code>protobuf-java</code> releases before 3.25.5 (per the upstream advisory the
-flaw was introduced at version 0, and is fixed …</p></summary><content type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.</p>
+<p>Solr is <strong>not affected</strong>. The crafted-message DoS requires an attacker to feed protobuf input to a
+parser, and Solr exposes no such path …</p></summary><content type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.</p>
+<p>Solr is <strong>not affected</strong>. The crafted-message DoS requires an attacker to feed protobuf input to a
+parser, and Solr exposes no such path:</p>
+<ul>
+<li><strong>Solr's own code never uses protobuf.</strong> There is no <code>com.google.protobuf</code> usage anywhere in the
+ Solr codebase, and Solr's client-facing APIs speak javabin, JSON and XML — never protobuf. The SQL
+ module is reached through <code>SQLHandler</code> (Calcite runs in-process, returning tuples); Solr exposes no
+ Avatica/protobuf wire endpoint to clients.</li>
+<li><strong>protobuf-java is only used to talk to trusted infrastructure.</strong> It is pulled in transitively for
+ communication with operator-controlled endpoints — the ZooKeeper ensemble, Hadoop RPC (HDFS /
+ Kerberos), the Google Cloud Storage backup API, the OpenTelemetry OTLP collector, and the Kafka
+ cross-DC pipeline. An external attacker cannot supply the deeply-nested message the DoS requires to
+ any of those parsers.</li>
+</ul>
+<p>Tracked upstream as SOLR-17833.</p>
<p>CVE-2024-7254 affects all <code>protobuf-java</code> releases before 3.25.5 (per the upstream advisory the
flaw was introduced at version 0, and is fixed in 3.25.5 / 4.27.5 / 4.28.2). Apache Solr has bundled
<code>protobuf-java</code> (transitively, via Hadoop and ZooKeeper) since <strong>Solr 4.4.0</strong> (which shipped 2.4.0a),
@@ -2042,5 +2312,4 @@ ship any Struts jar — the dependency is excluded and only appears as a transit
(see SOLR-2849) — so these Struts vulnerabilities …</p></summary><content type="html"><p>Scanners flag <code>velocity-tools-2.0.jar</code> with Apache Struts 1 CVEs because its POM declares a
transitive dependency on <code>struts-core</code>, <code>struts-taglib</code> and <code>struts-tiles</code> 1.3.8. Solr does not
ship any Struts jar — the dependency is excluded and only appears as a transitive POM listing
-(see SOLR-2849) — so these Struts vulnerabilities are not present in, or exploitable through, Solr.</p></content><category term="solr/vex"/></entry><entry><title>vorbis-java-tika</title><link href="/cve-2016-6809.html" rel="alternate"/><published>2022-12-14T00:00:00+00:00</published><updated>2022-12-14T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2022-12-14:/cve-2016-6809.html</id><content type="html"><p>See https://github.com/Gagravarr/Vo [...]
-<p>Tika as an in-process component was removed in Solr 9.11.</p></content><category term="solr/vex"/></entry><entry><title>org.restlet</title><link href="/cve-2017-14868.html" rel="alternate"/><published>2022-12-14T00:00:00+00:00</published><updated>2022-12-14T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2022-12-14:/cve-2017-14868.html</id><content type="html"><p>Solr should not be exposed outside a firewall where bad actors can send [...]
\ No newline at end of file
+(see SOLR-2849) — so these Struts vulnerabilities are not present in, or exploitable through, Solr.</p></content><category term="solr/vex"/></entry></feed>
\ No newline at end of file
diff --git a/output/feeds/solr/vex.atom.xml b/output/feeds/solr/vex.atom.xml
index 012843dab..05f65b982 100644
--- a/output/feeds/solr/vex.atom.xml
+++ b/output/feeds/solr/vex.atom.xml
@@ -1,5 +1,252 @@
<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr - solr/vex</title><link href="/" rel="alternate"/><link href="/feeds/solr/vex.atom.xml" rel="self"/><id>/</id><updated>2026-07-18T00:00:00+00:00</updated><entry><title>Apache Commons BeanUtils: class-loader access via a 'declaredClass' property path</title><link href="/cve-2025-48734.html" rel="alternate"/><published>2026-07-18T00:00:00+00:00</published><updated>2026-07-18T00:00:00+00:00</updated><author><name>Solr Developers</ [...]
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Apache Solr - solr/vex</title><link href="/" rel="alternate"/><link href="/feeds/solr/vex.atom.xml" rel="self"/><id>/</id><updated>2026-07-31T00:00:00+00:00</updated><entry><title>Apache Avro (Java): RCE reading a crafted schema / DoS deserializing untrusted data</title><link href="/cve-2024-47561.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers [...]
+an attacker-controlled Avro <strong>schema</strong> can instantiate arbitrary classes (affects avro &lt; 1.11.4).
+CVE-2023-39410 is a memory-exhaustion / DoS issue when <strong>deserializing untrusted Avro data</strong> (affects
+avro &lt; 1.11.3). Both require the application to feed attacker-controlled Avro …</p></summary><content type="html"><p>CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing
+an attacker-controlled Avro <strong>schema</strong> can instantiate arbitrary classes (affects avro &lt; 1.11.4).
+CVE-2023-39410 is a memory-exhaustion / DoS issue when <strong>deserializing untrusted Avro data</strong> (affects
+avro &lt; 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>Solr does not use Apache Avro.</strong> There is no <code>org.apache.avro</code> usage anywhere in the Solr
+ codebase, and Solr ships no standalone <code>avro-*.jar</code>. Avro appears only as an embedded/transitive
+ artifact of the optional Hadoop integration (the <code>hdfs</code> / <code>hadoop-auth</code> modules, which are not part
+ of a default install).</li>
+<li><strong>The vulnerable entry points are never reached.</strong> Solr never parses an externally-supplied Avro
+ schema and never deserializes untrusted Avro data — the only code that pulls Avro in is Hadoop's
+ own internal machinery, driven by administrator-supplied configuration, not by untrusted request
+ input.</li>
+</ul>
+<p>The affected range covers the 9.x line, where the optional Hadoop modules transitively carry Avro
+1.9.2; Solr's own code path never invokes it.</p></content><category term="solr/vex"/></entry><entry><title>jackson-core: memory disclosure via source snippet in JsonLocation error messages</title><link href="/cve-2025-49128.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-49128.html</id><summary type="html"><p>CVE-2025-49128 can dis [...]
+includes in <code>JsonLocation</code> (e.g. surfaced in parse-error messages). It affects jackson-core &lt; 2.13.0.</p>
+<p>Solr is <strong>not affected</strong>. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 — both …</p></summary><content type="html"><p>CVE-2025-49128 can disclose adjacent buffer memory through the source snippet that jackson-core
+includes in <code>JsonLocation</code> (e.g. surfaced in parse-error messages). It affects jackson-core &lt; 2.13.0.</p>
+<p>Solr is <strong>not affected</strong>. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 — both
+well past the 2.13.0 fix. The <code>2.12.7</code> copy a scanner flags is Hadoop's shaded jackson-core,
+reachable only via the optional Hadoop modules, which parse administrator-supplied configuration
+rather than untrusted external JSON, and whose parse errors are not returned to remote clients.</p></content><category term="solr/vex"/></entry><entry><title>jackson-core: async-parser number-length bypass and deep-nesting StackOverflow (DoS)</title><link href="/cve-2025-52999.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-52999.html</id [...]
+(an incomplete fix for GHSA-72hv-8253-57qq; affects &lt; 2.18.8 and 2.19.0–2.21.3). CVE-2025-52999 is a
+<code>StackOverflowError</code> when parsing <strong>very deeply nested</strong> input (affects &lt; 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The async parser is never used …</strong></li></ul></summary><content type="html"><p>GHSA-r7wm-3cxj-wff9 is a <code>maxNumberLength</code> bypass in jackson-core's <strong>async / non-blocking</strong> parser
+(an incomplete fix for GHSA-72hv-8253-57qq; affects &lt; 2.18.8 and 2.19.0–2.21.3). CVE-2025-52999 is a
+<code>StackOverflowError</code> when parsing <strong>very deeply nested</strong> input (affects &lt; 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The async parser is never used.</strong> Solr deserializes JSON with the standard <em>synchronous</em> Jackson
+ parser; it never calls the non-blocking <code>NonBlockingByteArrayParser</code> API, so the async-only
+ <code>maxNumberLength</code> bypass (GHSA-r7wm) is unreachable — as already assessed for GHSA-72hv-8253-57qq.</li>
+<li><strong>Solr's own jackson-core is patched.</strong> The bundled jackson-core is 2.18.0 in current 9.x and
+ 2.22.0 in 9.11 — both fixed for the deep-nesting StackOverflow (fixed in 2.15.0). The <code>2.12.7</code>
+ copy a scanner flags is Hadoop's <strong>shaded</strong> jackson, reachable only through the optional Hadoop
+ modules, which parse administrator-supplied configuration rather than untrusted external JSON.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>Nimbus JOSE + JWT: uncontrolled recursion (DoS) parsing crafted JOSE objects</title><link href="/cve-2025-53864.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2025-53864.html</id><summary type="html"><p>CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Ni [...]
+parsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x &lt; 9.37.4 and 10.0.x &lt; 10.0.2).</p>
+<p>Solr is <strong>not affected</strong>. Solr's JWT authentication (the optional <code>jwt-auth</code> module, <code>JWTAuthPlugin</code>)
+parses and validates tokens exclusively …</p></summary><content type="html"><p>CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Nimbus JOSE + JWT library when
+parsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x &lt; 9.37.4 and 10.0.x &lt; 10.0.2).</p>
+<p>Solr is <strong>not affected</strong>. Solr's JWT authentication (the optional <code>jwt-auth</code> module, <code>JWTAuthPlugin</code>)
+parses and validates tokens exclusively with <strong>jose4j</strong> (<code>org.jose4j.*</code> — the plugin imports jose4j
+and does not reference <code>com.nimbusds</code> at all). Nimbus JOSE + JWT is not on Solr's JWT-processing code
+path; it appears only as a transitive/declared reference and is never invoked to parse an incoming
+token, so the vulnerable recursive parser cannot be reached by an attacker-supplied JWT.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: Digest authentication lossy encoding</title><link href="/cve-2026-10050.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-10050.html</id><summary type="html"><p>CVE-2026- [...]
+(in <code>jetty-security</code>), which can weaken Digest credential handling. It affects the Jetty branches
+Solr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12 …</p></summary><content type="html"><p>CVE-2026-10050 is a lossy-encoding flaw in Eclipse Jetty's <strong>Digest authentication</strong> implementation
+(in <code>jetty-security</code>), which can weaken Digest credential handling. It affects the Jetty branches
+Solr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12.1.10).</p>
+<p>Solr is <strong>not affected</strong>. Solr bundles <code>jetty-security</code> as part of the Jetty server stack, but it
+does not use Jetty's declarative security: it never installs a Jetty <code>SecurityHandler</code> /
+<code>ConstraintSecurityHandler</code> and never configures a Jetty <code>Authenticator</code> (Digest or otherwise). Solr
+authenticates requests in its own servlet filter (<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code>
+framework — Basic, JWT, Kerberos, PKI, etc.), so Jetty's Digest-authentication code path — the code
+this CVE affects — is never invoked. The affected range spans the releases whose bundled Jetty is in
+an affected branch (Solr 7.3.0 – 10.0.0).</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: HTTP/1.1 request trailers leak across keep-alive requests</title><link href="/cve-2026-10051.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-10051.html</id><summary type="html"><p>CVE-2026-10051 is an information-ex [...]
+not reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request
+can be observed via <code>getTrailers()</code> on a later request on the same connection. It has security impact
+only for applications that …</p></summary><content type="html"><p>CVE-2026-10051 is an information-exposure bug in Jetty's <code>HttpConnection</code>: the <code>_trailers</code> field is
+not reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request
+can be observed via <code>getTrailers()</code> on a later request on the same connection. It has security impact
+only for applications that <strong>read HTTP trailers</strong> (<code>request.getTrailers()</code>) and use them for logic or
+security decisions.</p>
+<p>Solr is <strong>not affected</strong>. Solr does not read HTTP request trailers anywhere — there is no
+<code>getTrailers()</code> / trailer-field usage in the Solr codebase — so stale trailer state on a pooled
+connection is never observed by Solr and cannot influence request handling or authorization. The
+affected range spans the releases whose bundled Jetty is in an affected branch (Solr 7.3.0 – 10.0.0).</p></content><category term="solr/vex"/></entry><entry><title>Apache Thrift (Java): TLS hostname verification in TSSLTransportFactory</title><link href="/cve-2026-43869.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-43869.html</id><summa [...]
+<code>TSSLTransportFactory</code> (affects libthrift ≤ 0.22.0, fixed in 0.23.0): a client using Thrift's TLS
+transport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on
+that connection.</p>
+<p>Solr is <strong>not affected</strong> in any default or recommended configuration …</p></summary><content type="html"><p>CVE-2026-43869 is a TLS hostname-verification weakness in Apache Thrift's
+<code>TSSLTransportFactory</code> (affects libthrift ≤ 0.22.0, fixed in 0.23.0): a client using Thrift's TLS
+transport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on
+that connection.</p>
+<p>Solr is <strong>not affected</strong> in any default or recommended configuration. <code>libthrift</code> is bundled only by
+the optional, opt-in <strong><code>jaegertracer-configurator</code></strong> module (Jaeger distributed-tracing exporter) —
+it is not part of a default Solr install, and Solr does not use Thrift's TLS transport anywhere else.
+Even when Jaeger tracing is enabled, Solr exports spans to an <strong>operator-configured</strong> Jaeger backend
+(a trusted, first-party collector), not to an untrusted remote host, so there is no untrusted TLS
+peer for the missing hostname check to expose. The issue is only relevant to an operator who both
+enables Jaeger tracing and deliberately points it at an untrusted TLS endpoint.</p></content><category term="solr/vex"/></entry><entry><title>Apache Commons Configuration: StackOverflowError for YAML input with cycles</title><link href="/cve-2026-45205.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-45205.html</id><summary type="html">< [...]
+containing reference cycles (affects 2.2 – 2.14.x, fixed in 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>. Solr uses <code>commons-configuration2</code> only transitively, via the optional
+Hadoop integration (Kerberos / HDFS support), to load <strong>administrator-supplied</strong> Hadoop configuration
+files — not …</p></summary><content type="html"><p>CVE-2026-45205 is a <code>StackOverflowError</code> (DoS) when Apache Commons Configuration parses YAML input
+containing reference cycles (affects 2.2 – 2.14.x, fixed in 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>. Solr uses <code>commons-configuration2</code> only transitively, via the optional
+Hadoop integration (Kerberos / HDFS support), to load <strong>administrator-supplied</strong> Hadoop configuration
+files — not untrusted, externally-supplied YAML. No Solr request path feeds attacker-controlled YAML
+to Commons Configuration, so the cyclic-YAML parser cannot be driven by an adversary. (This matches
+the existing assessment of the other Commons Configuration CVEs in Solr.)</p></content><category term="solr/vex"/></entry><entry><title>Apache Calcite: arbitrary class loading via a user-controlled model</title><link href="/cve-2026-46718.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-46718.html</id><summary type="html"><p>CVE-2026 [...]
+execution (affects calcite-core 1.5.0 – 1.41.x, fixed in 1.42.0). Exploitation requires the
+application to let an attacker supply the Calcite <em>model</em> (the JSON schema/model definition that can
+name factory classes).</p>
+<p>Solr is …</p></summary><content type="html"><p>CVE-2026-46718 lets a <strong>user-controlled Calcite model</strong> load arbitrary classes, leading to code
+execution (affects calcite-core 1.5.0 – 1.41.x, fixed in 1.42.0). Exploitation requires the
+application to let an attacker supply the Calcite <em>model</em> (the JSON schema/model definition that can
+name factory classes).</p>
+<p>Solr is <strong>not affected</strong>. Calcite is used only by the optional <code>sql</code> module (Parallel SQL, the <code>/sql</code>
+handler). Solr constructs the Calcite schema/model <strong>server-side</strong> from the target collection; users
+submit only a SQL statement, never a Calcite model or schema-factory definition. There is no request
+path through which an attacker can supply a Calcite model, so the arbitrary-class-loading vector is
+never reached.</p></content><category term="solr/vex"/></entry><entry><title>jackson-databind: nested-toString DoS, InetSocketAddress SSRF, and deserialization-filter bypasses</title><link href="/cve-2026-50193.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-50193.html</id><summary type="html"><p>Four jackson-databind issues, in two [...]
+<ul>
+<li><strong>Only the Hadoop-shaded old copy is affected.</strong> CVE-2026-50193 (StackOverflow on <code>toString()</code> of a
+ deeply-nested <code>JsonNode</code>, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when
+ deserializing into <code>InetSocketAddress</code>, fixed 2.18.8 / 2.21.4) do not affect Solr's own
+ jackson-databind (2.18 …</li></ul></summary><content type="html"><p>Four jackson-databind issues, in two groups:</p>
+<ul>
+<li><strong>Only the Hadoop-shaded old copy is affected.</strong> CVE-2026-50193 (StackOverflow on <code>toString()</code> of a
+ deeply-nested <code>JsonNode</code>, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when
+ deserializing into <code>InetSocketAddress</code>, fixed 2.18.8 / 2.21.4) do not affect Solr's own
+ jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 — both patched). The <code>2.12.7.1</code> a scanner
+ flags is Hadoop's shaded copy, reachable only through the optional Hadoop modules, which process
+ administrator-supplied configuration rather than untrusted external JSON.</li>
+<li><strong>Require Jackson features Solr does not use.</strong> CVE-2026-54515 (case-insensitive deserialization
+ bypassing per-property <code>@JsonIgnoreProperties</code>), CVE-2026-59889 (<code>@JsonView</code> bypass for
+ <code>@JsonUnwrapped</code> container properties), CVE-2026-59888 (<code>@JsonIgnore</code> on a Record property bypassed
+ via a <code>PropertyNamingStrategy</code>), and GHSA-mhm7-754m-9p8w (<code>@JsonView</code> bypass for creator properties
+ with <code>@JsonTypeInfo(include = As.EXTERNAL_PROPERTY)</code>) can reach Solr's own jackson-databind, but
+ only when an application relies on those annotation-based mechanisms — case-insensitive property
+ mapping, <code>@JsonView</code>, <code>@JsonUnwrapped</code>, <code>@JsonIgnore</code> on records, or <code>@JsonTypeInfo</code> external-property
+ polymorphism — to restrict which fields untrusted input may set. Solr uses none of them: it maps
+ request JSON to fixed, known types and never applies <code>@JsonView</code>/<code>@JsonIgnore</code>-based deserialization
+ filtering or polymorphic typing to untrusted input, so these bypasses have nothing to bypass.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>jackson-databind: PolymorphicTypeValidator allowlist bypasses (unsafe deserialization)</title><link href="/cve-2026-54512.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-54512.html</id><summary type="html"><p>CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-dat [...]
+generic type parameters (54512) and via an array-subtype allowlist gap in
+<code>allowIfSubType</code> (54513) — that can let unexpected classes be instantiated during polymorphic
+deserialization (affects 2.10.0–2.18.7 and 2.19.0–2.21.3).</p>
+<p>Solr is <strong>not affected …</strong></p></summary><content type="html"><p>CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's <code>PolymorphicTypeValidator</code> — via
+generic type parameters (54512) and via an array-subtype allowlist gap in
+<code>allowIfSubType</code> (54513) — that can let unexpected classes be instantiated during polymorphic
+deserialization (affects 2.10.0–2.18.7 and 2.19.0–2.21.3).</p>
+<p>Solr is <strong>not affected</strong>. Both issues are only exploitable when an application enables <strong>polymorphic
+deserialization</strong> — default typing (<code>activateDefaultTyping</code>), <code>@JsonTypeInfo</code>, or a
+<code>BasicPolymorphicTypeValidator</code> allowlist — and then deserializes attacker-controlled JSON through it.
+Solr does none of this: it maps request JSON to fixed, known target types and never enables default
+typing or polymorphic deserialization of untrusted input, so the <code>PolymorphicTypeValidator</code> code path
+these CVEs target is never exercised. (The <code>2.12.7.1</code> copy a scanner flags is Hadoop's shaded
+jackson-databind; Solr's own is 2.18.0 in current 9.x and 2.22.0 in 9.11.)</p></content><category term="solr/vex"/></entry><entry><title>JLine: unauthenticated remote DoS in the Telnet server</title><link href="/cve-2026-56740.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-56740.html</id><summary type="html"><p>CVE-2026-56740 and C [...]
+Telnet server</strong> — unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values
+(56741) in the <code>jline-remote-telnet</code> Telnet daemon (affects &lt; 3.30.14, and the 4.0.x / 4.1.x lines).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The vulnerable component is not shipped …</strong></li></ul></summary><content type="html"><p>CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in <strong>JLine's
+Telnet server</strong> — unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values
+(56741) in the <code>jline-remote-telnet</code> Telnet daemon (affects &lt; 3.30.14, and the 4.0.x / 4.1.x lines).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The vulnerable component is not shipped or run.</strong> Solr ships no <code>jline-remote-telnet</code> jar; the
+ <code>3.9.0</code> coordinate a scanner reports comes only from a dependency reference embedded in the bundled
+ <code>zookeeper-3.9.5</code> jar's metadata. Solr never starts a JLine Telnet server (<code>Telnetd</code>).</li>
+<li>JLine is used, at most, for the local interactive <code>bin/solr</code> CLI terminal — a <code>LineReader</code> on the
+ operator's own console, not a network-listening Telnet daemon — so nothing accepts remote Telnet
+ connections that the vulnerable NAWS/NEW-ENVIRON parsing could act on.</li>
+</ul></content><category term="solr/vex"/></entry><entry><title>Netty codec: SPDY / HTTP2-decompression / Bzip2 denial-of-service issues</title><link href="/cve-2026-56745.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-56745.html</id><summary type="html"><p>These five Netty issues are resource-exhaustion / DoS bugs in server- and d [...]
+(all affect Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 — the <strong>SPDY</strong> codec (<code>SpdyHttpDecoder</code> and SPDY
+ header/settings handling) in <code>netty-codec-http</code>.</li>
+<li>CVE-2026-56819 …</li></ul></summary><content type="html"><p>These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths
+(all affect Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 — the <strong>SPDY</strong> codec (<code>SpdyHttpDecoder</code> and SPDY
+ header/settings handling) in <code>netty-codec-http</code>.</li>
+<li>CVE-2026-56819 — server-side <strong>HTTP/2 decompression</strong> ByteBuf reference leak in <code>netty-codec-http2</code>.</li>
+<li>CVE-2026-59901 — infinite loop in the <strong>Bzip2</strong> decoder in <code>netty-codec-compression</code>.</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty acts strictly as a <strong>client</strong>. Solr's HTTP server is Jetty, not
+Netty: Solr never runs a Netty HTTP/HTTP2/SPDY server, never enables the SPDY codec, and never feeds
+attacker-controlled compressed (bzip2) streams through Netty. The vulnerable server/decoder code
+paths are therefore unreachable — the same reasoning as CVE-2026-33870 / CVE-2026-33871.</p></content><category term="solr/vex"/></entry><entry><title>Netty codec-http/http2: server-side HTTP handling issues (DoS, CORS/WebSocket, smuggling, CRLF)</title><link href="/cve-2026-59899.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-59899.html [...]
+Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-59899 — unbounded per-connection queue growth in <code>HttpContentEncoder</code> via HTTP/1.1
+ pipelining (server response encoding …</li></ul></summary><content type="html"><p>These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect
+Netty &lt; 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-59899 — unbounded per-connection queue growth in <code>HttpContentEncoder</code> via HTTP/1.1
+ pipelining (server response encoding).</li>
+<li>CVE-2026-56746 — CORS short-circuit failure / security-control bypass (server CORS handler).</li>
+<li>CVE-2026-59898 — WebSocket V07/V08 handshaker missing Connection/Upgrade validation (server).</li>
+<li>CVE-2026-59921 — CRLF injection via multipart filename in the outbound <code>HttpPostRequestEncoder</code>.</li>
+<li>CVE-2026-59900 — Host-header de-duplication gap in HTTP/2→HTTP/1.x translation (server/proxy).</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty is used strictly as a <strong>client</strong>. Solr's HTTP server is Jetty:
+Solr never runs a Netty HTTP server, CORS handler, WebSocket server, or HTTP/2→1 proxy, and never
+uses Netty's multipart request encoder, so none of these code paths are reachable.</p></content><category term="solr/vex"/></entry><entry><title>lz4-java: out-of-bounds read via invalid arguments to native XXHash</title><link href="/cve-2026-59949.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-59949.html</id><summary type="html"><p> [...]
+JNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that
+passes an invalid array reference or an out-of-range <code>off</code>/<code>len</code> to the native XXHash methods can
+crash the JVM. It affects lz4-java …</p></summary><content type="html"><p>CVE-2026-59949 (CVSS 6.5) is an out-of-bounds read in the <code>at.yawk.lz4:lz4-java</code> codec: the
+JNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that
+passes an invalid array reference or an out-of-range <code>off</code>/<code>len</code> to the native XXHash methods can
+crash the JVM. It affects lz4-java ≤ 1.11.0 (fixed in 1.11.1). Exploitation requires an application
+to pass attacker-influenced array/offset/length values into those XXHash APIs.</p>
+<p>Solr is <strong>not affected</strong>. <code>lz4-java</code> is bundled only by the optional <code>cross-dc</code> module, where it is
+used by the embedded Apache Kafka client for LZ4 compression / checksums of cross-datacenter
+replication messages. Kafka calls the XXHash APIs with its own internally-managed, validated buffers
+and offsets — it does not forward attacker-controlled <code>off</code>/<code>len</code> values into the native methods —
+and the replication stream flows through an operator-controlled Kafka pipeline, not untrusted
+external input. The <code>cross-dc</code> module is not part of a default Solr installation, and no Solr request
+path reaches the vulnerable XXHash argument handling.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: HTTP/2 :authority vs Host header confusion</title><link href="/cve-2026-6790.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-6790.html</id><summary type="html"><p>CVE-2026-6790 is an input-validation gap [...]
+does not require the <code>:authority</code> pseudo-header to match the <code>Host</code> header, so a single request can
+carry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x
+through …</p></summary><content type="html"><p>CVE-2026-6790 is an input-validation gap in Jetty's HTTP/2 (and HTTP/3) request processing: Jetty
+does not require the <code>:authority</code> pseudo-header to match the <code>Host</code> header, so a single request can
+carry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x
+through 10.0.26, 12.0.x through 12.0.34). It has security impact only for applications that <strong>make
+security-sensitive decisions based on the request host</strong> — host-based access control, virtual-host
+isolation, multi-tenant routing, or host-derived redirect URLs.</p>
+<p>Solr is <strong>not affected</strong>. Solr does none of those things: it does not perform host-based access
+control or virtual-host/multi-tenant isolation, its authentication and authorization
+(<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code> framework) never key on the <code>Host</code>/<code>:authority</code>
+value, and it does not build security-sensitive redirects from the request host. With no
+host-dependent security decision, the host-confusion has no exploitable consequence in Solr.</p></content><category term="solr/vex"/></entry><entry><title>Eclipse Jetty: non-canonical URL paths in URIUtil.canonicalPath (authorization bypass)</title><link href="/cve-2026-8384.html" rel="alternate"/><published>2026-07-31T00:00:00+00:00</published><updated>2026-07-31T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-31:/cve-2026-8384.html</id><s [...]
+path-parameter marker before dot-dot segments (e.g. <code>/public;/../admin/secret</code>) is not normalized,
+so a path-prefix authorization check can be bypassed. It is exploitable by applications that use
+Jetty's <code>SecurityHandler.PathMapped</code>, or that make an authorization decision on a …</p></summary><content type="html"><p>CVE-2026-8384 is a path-canonicalization flaw in Jetty's <code>URIUtil.canonicalPath()</code>: a semicolon
+path-parameter marker before dot-dot segments (e.g. <code>/public;/../admin/secret</code>) is not normalized,
+so a path-prefix authorization check can be bypassed. It is exploitable by applications that use
+Jetty's <code>SecurityHandler.PathMapped</code>, or that make an authorization decision on a canonicalized path
+at a <strong>different layer</strong> than the one that ultimately dispatches the request (the classic
+canonicalization <em>desync</em>).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>No desync between authorization and dispatch.</strong> <code>HttpSolrCall</code> computes the request path once
+ (<code>ServletUtils.getPathAfterContext()</code>), and uses that single value for <em>both</em> request routing
+ (<code>getPath()</code>) and authorization (<code>getAuthCtx()</code> builds its <code>AuthorizationContext</code> resource from the
+ same <code>getPath()</code>). <code>RuleBasedAuthorizationPlugin</code> therefore evaluates exactly the path that Solr
+ dispatches — there is no window in which authorization sees one path while a different path is
+ served, which is the precondition this CVE requires.</li>
+<li><strong>Path parameters are already stripped.</strong> Solr derives the path from <code>getServletPath()</code> +
+ <code>getPathInfo()</code>, which per the Servlet specification have path parameters (the <code>;…</code> segments this
+ bug abuses) removed by the container before Solr ever sees the path.</li>
+<li>Solr uses neither Jetty's <code>SecurityHandler.PathMapped</code> nor <code>URIUtil.canonicalPath()</code> directly.</li>
+</ul>
+<p>So even on an affected Jetty, the mis-canonicalization cannot produce an authorization bypass in
+Solr, because Solr's authorization and dispatch are driven by the same, single path value.</p></content><category term="solr/vex"/></entry><entry><title>Apache Commons BeanUtils: class-loader access via a 'declaredClass' property path</title><link href="/cve-2025-48734.html" rel="alternate"/><published>2026-07-18T00:00:00+00:00</published><updated>2026-07-18T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-07-18:/cve-2025-48734.html</id><summar [...]
<p>CVE-2025-48734 affects all Commons BeanUtils 1.x releases before 1.11.0. Solr has bundled
commons-beanutils since Solr 3.6.0, and every release that includes it, through Solr 10.0.0, ships an
affected 1.x version (1.7.0, then 1.8.3, 1.9.3 and 1.9.4 — all below 1.11.0). The affected range is
@@ -755,9 +1002,10 @@ who can supply a crafted dictionary file — either directly or embedded in a mo
OpenNLP deserializes — can therefore read local files from the server or trigger outbound requests
(server-side request forgery). Other OpenNLP XML parsing paths route through the hardened
<code>XmlUtil.createSaxParser()</code> helper, but this code path does not.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
-<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which parse dictionaries with secure
-XML processing that rejects DOCTYPE declarations and external entities.</p>
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed in OpenNLP 2.5.9 (and
+3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these parse dictionaries
+with secure XML processing that rejects DOCTYPE declarations and external entities.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable dictionary-parsing code path becomes reachable when:</p>
@@ -780,11 +1028,14 @@ archive passes through a single chokepoint before OpenNLP is allowed to deserial
to both standalone (filesystem configset) and SolrCloud (ZooKeeper) deployments, and whether the
dictionary is loaded by the <code>langid</code> / <code>analysis-extras</code> update processors or by the
schema-configured OpenNLP analyzers.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Arbitrary class instantiation via model manifest</title><link href="/cve-2026-42027.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve- [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Arbitrary class instantiation via model manifest</title><link href="/cve-2026-42027.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve-2026-42027.html</id><summary type="html"><p>CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue i [...]
<code>ExtensionLoader</code>. The <code>instantiateExtension(Class, String)</code> method loads a class named in a
model archive's <code>manifest.properties</code> via <code>Class.forName()</code> and only performs its
<code>isAssignableFrom</code> type check <em>after</em> the class has been loaded. Because <code>Class.forName()</code>
@@ -796,8 +1047,9 @@ runs the target class's static initializer at load time, an attacker who can sup
model archive can trigger the static initializer of any class on the classpath (e.g. one that
performs a JNDI lookup, outbound network I/O, or filesystem access), regardless of the
type check that follows.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively
-via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which consults a
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP
+2.5.9 (and 3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; the fix consults a
package-prefix allowlist <em>before</em> calling <code>Class.forName()</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
@@ -813,9 +1065,8 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>In Solr 9.11.0 the upstream allowlist defense is backfilled at the application layer, since the
-vulnerable jar cannot yet be upgraded (Solr must track the OpenNLP version used by
-<code>lucene-analysis-opennlp</code>). Every OpenNLP model is loaded as a resource through Solr's resource
+<p>As defense in depth, Solr 9.11 also validates OpenNLP models at the application layer before they
+reach <code>ExtensionLoader</code>. Every OpenNLP model is loaded as a resource through Solr's resource
loaders, so the archive is validated at that single chokepoint before OpenNLP is allowed to
deserialize it:</p>
<ul>
@@ -830,11 +1081,14 @@ deserialize it:</p>
</ul>
<p>Solr's own usage only ever references built-in <code>opennlp.*</code> factories, so legitimate models load
unchanged; only crafted models that try to instantiate arbitrary classes are blocked.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Out-of-memory denial of service via crafted model file</title><link href="/cve-2026-42440.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04 [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> is fixed — it upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the
+1.9.x backport) and adds the application-layer allowlist described above — and Solr <strong>10.1</strong> upgrades
+to 2.5.9. The affected (exploitable) range is therefore <strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 (plus Solr's
+own allowlist) closes this issue.</p></content><category term="solr/vex"/></entry><entry><title>Apache OpenNLP: Out-of-memory denial of service via crafted model file</title><link href="/cve-2026-42440.html" rel="alternate"/><published>2026-05-04T00:00:00+00:00</published><updated>2026-05-04T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-05-04:/cve-2026-42440.html</id><summary type="html"><p>CVE-2026-42440 (CVSS 7.5) is an out-of-memory [...]
model reader. The <code>AbstractModelReader</code> methods <code>getOutcomes()</code>, <code>getOutcomePatterns()</code> and
<code>getPredicates()</code> read a 32-bit signed integer count field from a binary model stream and pass it
directly to an array allocation without validating it. An attacker who can supply …</p></summary><content type="html"><p>CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary
@@ -845,9 +1099,9 @@ model file with a count set to <code>Integer.MAX_VALUE</code> trigge
model deserialization, before any substantial data is consumed.</p>
<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP 2.5.9 (and
-3.0.0-M3), and backported to the end-of-life 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these
-validate the count against an upper bound (default 10,000,000, configurable via the
-<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating.</p>
+3.0.0-M3), which validate the count against an upper bound (default 10,000,000, configurable via the
+<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating, and backported to the 1.9.x line as
+<code>opennlp-tools-1.9.5</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">&para;</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable model-loading code path becomes reachable when:</p>
@@ -864,12 +1118,14 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9. Solr has bundled OpenNLP (transitively,
-via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so every release from 7.3.0 through 10.0.0 ships an
-affected version (1.8.3 through 2.5.6). The affected range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fixed in Solr 9.11, which bundles the patched <code>opennlp-tools</code> 1.9.5, and in Solr 10.1, which upgrades
-the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9. Solr 10.0 remains affected (it ships
-OpenNLP 2.5.6).</p></content><category term="solr/vex"/></entry><entry><title>Apache Log4j Core: TLS hostname verification silently ignored in Socket, SMTP and Syslog appenders</title><link href="/cve-2026-34477.html" rel="alternate"/><published>2026-04-10T00:00:00+00:00</published><updated>2026-04-10T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-04-10:/cve-2026-34477.html</id><summary type="html"><p>CVE-2026-34477 is <strong>not [...]
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p></content><category term="solr/vex"/></entry><entry><title>Apache Log4j Core: TLS hostname verification silently ignored in Socket, SMTP and Syslog appenders</title><link href="/cve-2026-34477.html" rel="alternate"/><published>2026-04-10T00:00:00+00:00</published><updated>2026-04-10T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2026-04-10:/cve-2026-34477.html</id><summary type="html"><p>CVE-2026-34477 is <strong>not [...]
Successful exploitation requires a specific, non-default logging configuration together with a privileged network position.
The following conditions <strong>must all be met</strong>:</p>
<ul>
@@ -1019,8 +1275,22 @@ so dependency scanners flag the <code>commons-lang3</code> JAR bundl
(<code>solr-hadoop-auth</code>) to load administrator-provided Hadoop configuration files. Class names are not
attacker-controlled in that path, so the recursion cannot be driven by an adversary and the
vulnerability is not exploitable in Solr.</p></content><category term="solr/vex"/></entry><entry><title>protobuf-java: Potential Denial of Service issue</title><link href="/cve-2024-7254.html" rel="alternate"/><published>2025-08-02T00:00:00+00:00</published><updated>2025-08-02T00:00:00+00:00</updated><author><name>Solr Developers</name></author><id>tag:None,2025-08-02:/cve-2024-7254.html</id><summary type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Ful [...]
-<p>CVE-2024-7254 affects all <code>protobuf-java</code> releases before 3.25.5 (per the upstream advisory the
-flaw was introduced at version 0, and is fixed …</p></summary><content type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.</p>
+<p>Solr is <strong>not affected</strong>. The crafted-message DoS requires an attacker to feed protobuf input to a
+parser, and Solr exposes no such path …</p></summary><content type="html"><p>When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.</p>
+<p>Solr is <strong>not affected</strong>. The crafted-message DoS requires an attacker to feed protobuf input to a
+parser, and Solr exposes no such path:</p>
+<ul>
+<li><strong>Solr's own code never uses protobuf.</strong> There is no <code>com.google.protobuf</code> usage anywhere in the
+ Solr codebase, and Solr's client-facing APIs speak javabin, JSON and XML — never protobuf. The SQL
+ module is reached through <code>SQLHandler</code> (Calcite runs in-process, returning tuples); Solr exposes no
+ Avatica/protobuf wire endpoint to clients.</li>
+<li><strong>protobuf-java is only used to talk to trusted infrastructure.</strong> It is pulled in transitively for
+ communication with operator-controlled endpoints — the ZooKeeper ensemble, Hadoop RPC (HDFS /
+ Kerberos), the Google Cloud Storage backup API, the OpenTelemetry OTLP collector, and the Kafka
+ cross-DC pipeline. An external attacker cannot supply the deeply-nested message the DoS requires to
+ any of those parsers.</li>
+</ul>
+<p>Tracked upstream as SOLR-17833.</p>
<p>CVE-2024-7254 affects all <code>protobuf-java</code> releases before 3.25.5 (per the upstream advisory the
flaw was introduced at version 0, and is fixed in 3.25.5 / 4.27.5 / 4.28.2). Apache Solr has bundled
<code>protobuf-java</code> (transitively, via Hadoop and ZooKeeper) since <strong>Solr 4.4.0</strong> (which shipped 2.4.0a),
diff --git a/output/security-dependency-cves.html b/output/security-dependency-cves.html
index fd7863e78..54b500a1e 100644
--- a/output/security-dependency-cves.html
+++ b/output/security-dependency-cves.html
@@ -191,6 +191,159 @@ or contact <a href="mailto:security@apache.org">security@apache.org</a>.</p>
</tr>
<tr>
<td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-8384">CVE-2026-8384</a> </td>
+ <td>7.3.0-10.0.0</td>
+ <td>
+ jetty-util-10.0.26.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-8384">Eclipse Jetty: non-canonical URL paths in URIUtil.canonicalPath (authorization bypass)</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-6790">CVE-2026-6790</a> </td>
+ <td>7.3.0-10.0.0</td>
+ <td>
+ jetty-server-10.0.26.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-6790">Eclipse Jetty: HTTP/2 :authority vs Host header confusion</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59949">CVE-2026-59949</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ lz4-java-1.10.1.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-59949">lz4-java: out-of-bounds read via invalid arguments to native XXHash</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59899">CVE-2026-59899</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56746">CVE-2026-56746</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59898">CVE-2026-59898</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59921">CVE-2026-59921</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59900">CVE-2026-59900</a> </td>
+ <td>9.2.0-10.0.0</td>
+ <td>
+ netty-codec-http-4.2.15.Final.jar, netty-codec-http2-4.2.15.Final.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-59899">Netty codec-http/http2: server-side HTTP handling issues (DoS, CORS/WebSocket, smuggling, CRLF)</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56745">CVE-2026-56745</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55833">CVE-2026-55833</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55831">CVE-2026-55831</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56819">CVE-2026-56819</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59901">CVE-2026-59901</a> </td>
+ <td>9.2.0-10.0.0</td>
+ <td>
+ netty-codec-http-4.2.15.Final.jar, netty-codec-http2-4.2.15.Final.jar, netty-codec-compression-4.2.15.Final.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-56745">Netty codec: SPDY / HTTP2-decompression / Bzip2 denial-of-service issues</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56740">CVE-2026-56740</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56741">CVE-2026-56741</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ jline-remote-telnet-3.9.0.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-56740">JLine: unauthenticated remote DoS in the Telnet server</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54512">CVE-2026-54512</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54513">CVE-2026-54513</a> </td>
+ <td>4.7.0-10.0.0</td>
+ <td>
+ jackson-databind-2.12.7.1.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-54512">jackson-databind: PolymorphicTypeValidator allowlist bypasses (unsafe deserialization)</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-50193">CVE-2026-50193</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54514">CVE-2026-54514</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54515">CVE-2026-54515</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59889">CVE-2026-59889</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59888">CVE-2026-59888</a>, <a href="https://github.com/advisories/GHSA-mhm7-754m-9p8w">GHSA-mhm7-754m-9p8w</a> </td>
+ <td>4.7.0-10.0.0</td>
+ <td>
+ jackson-databind-2.12.7.1.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-50193">jackson-databind: nested-toString DoS, InetSocketAddress SSRF, and deserialization-filter bypasses</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-46718">CVE-2026-46718</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ calcite-core-1.37.0.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-46718">Apache Calcite: arbitrary class loading via a user-controlled model</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-45205">CVE-2026-45205</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ commons-configuration2-2.10.1.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-45205">Apache Commons Configuration: StackOverflowError for YAML input with cycles</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-43869">CVE-2026-43869</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ libthrift-0.15.0.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-43869">Apache Thrift (Java): TLS hostname verification in TSSLTransportFactory</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10051">CVE-2026-10051</a> </td>
+ <td>7.3.0-10.0.0</td>
+ <td>
+ jetty-server-10.0.26.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-10051">Eclipse Jetty: HTTP/1.1 request trailers leak across keep-alive requests</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10050">CVE-2026-10050</a> </td>
+ <td>7.3.0-10.0.0</td>
+ <td>
+ jetty-security-10.0.26.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2026-10050">Eclipse Jetty: Digest authentication lossy encoding</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2025-53864">CVE-2025-53864</a> </td>
+ <td>9.0.0-10.0.0</td>
+ <td>
+ nimbus-jose-jwt-9.37.2.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2025-53864">Nimbus JOSE + JWT: uncontrolled recursion (DoS) parsing crafted JOSE objects</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://github.com/advisories/GHSA-r7wm-3cxj-wff9">GHSA-r7wm-3cxj-wff9</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-52999">CVE-2025-52999</a> </td>
+ <td>4.7.0-10.0.0</td>
+ <td>
+ jackson-core-2.12.7.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2025-52999">jackson-core: async-parser number-length bypass and deep-nesting StackOverflow (DoS)</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2025-49128">CVE-2025-49128</a> </td>
+ <td>4.7.0-10.0.0</td>
+ <td>
+ jackson-core-2.12.7.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2025-49128">jackson-core: memory disclosure via source snippet in JsonLocation error messages</a></td>
+ </tr>
+ <tr>
+ <td>
+<a href="https://nvd.nist.gov/vuln/detail/CVE-2024-47561">CVE-2024-47561</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-39410">CVE-2023-39410</a> </td>
+ <td>9.0.0-9.10.1</td>
+ <td>
+ avro-1.9.2.jar </td>
+ <td><span class="cdx-not-affected">not affected</span></td>
+ <td><a href="/vex.html#cve-2024-47561">Apache Avro (Java): RCE reading a crafted schema / DoS deserializing untrusted data</a></td>
+ </tr>
+ <tr>
+ <td>
<a href="https://github.com/advisories/GHSA-72hv-8253-57qq">GHSA-72hv-8253-57qq</a> </td>
<td>4.7.0-10.0.0</td>
<td>
@@ -399,7 +552,7 @@ or contact <a href="mailto:security@apache.org">security@apache.org</a>.</p>
<tr>
<td>
<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-42440">CVE-2026-42440</a> </td>
- <td>7.3.0-10.0.0</td>
+ <td>7.3.0-9.10.1,10.0.0</td>
<td>
opennlp-tools-1.9.4.jar </td>
<td><span class="cdx-exploitable">exploitable</span></td>
@@ -408,7 +561,7 @@ or contact <a href="mailto:security@apache.org">security@apache.org</a>.</p>
<tr>
<td>
<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-42027">CVE-2026-42027</a> </td>
- <td>7.3.0-10.0.0</td>
+ <td>7.3.0-9.10.1,10.0.0</td>
<td>
opennlp-tools-1.9.4.jar </td>
<td><span class="cdx-exploitable">exploitable</span></td>
@@ -417,7 +570,7 @@ or contact <a href="mailto:security@apache.org">security@apache.org</a>.</p>
<tr>
<td>
<a href="https://nvd.nist.gov/vuln/detail/CVE-2026-40682">CVE-2026-40682</a> </td>
- <td>7.3.0-10.0.0</td>
+ <td>7.3.0-9.10.1,10.0.0</td>
<td>
opennlp-tools-1.9.4.jar </td>
<td><span class="cdx-exploitable">exploitable</span></td>
@@ -483,7 +636,7 @@ or contact <a href="mailto:security@apache.org">security@apache.org</a>.</p>
<td>4.4.0-9.9.0</td>
<td>
protobuf-java-3.25.3.jar </td>
- <td><span class="cdx-in-triage">in triage</span></td>
+ <td><span class="cdx-not-affected">not affected</span></td>
<td><a href="/vex.html#cve-2024-7254">protobuf-java: Potential Denial of Service issue</a></td>
</tr>
<tr>
diff --git a/output/solr.openvex.json b/output/solr.openvex.json
index a055f5a33..a25457c23 100644
--- a/output/solr.openvex.json
+++ b/output/solr.openvex.json
@@ -2,7 +2,7 @@
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://solr.apache.org/solr.openvex.json",
"author": "Apache Solr Project (security@apache.org)",
- "timestamp": "2026-07-18T00:00:00Z",
+ "timestamp": "2026-07-31T00:00:00Z",
"version": 1,
"statements": [
{
@@ -1054,9 +1054,11 @@
"@id": "pkg:maven/com.google.protobuf/protobuf-java@3.6.1"
}
],
- "status": "under_investigation",
+ "status": "not_affected",
"timestamp": "2025-08-02T00:00:00Z",
- "status_notes": "Affected Apache Solr versions: 4.4.0-9.9.0. When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.\n\nCVE-2024-7254 affects all `protobuf-java` releases before 3.25.5 (per the upstream advisory the\nflaw was introduced at version 0, and is fixed in 3.25.5 / 4.27.5 / 4.28.2). Apache Solr has bundled\n`protobuf-java` (transitively, via Hadoop and ZooKeeper) sin [...]
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.\n\nSolr is **not affected**. The crafted-message DoS requires an attacker to feed protobuf input to a\nparser, and Solr exposes no such path:\n\n* **Solr's own code never uses protobuf.** There is no `com.google.protobuf` usage anywhere in the\n Solr codebase, and Solr's client-facing APIs speak java [...]
+ "status_notes": "Affected Apache Solr versions: 4.4.0-9.9.0."
},
{
"vulnerability": {
@@ -1179,8 +1181,8 @@
],
"status": "affected",
"timestamp": "2026-05-04T00:00:00Z",
- "action_statement": "CVE-2026-40682 (CVSS 9.1) is an XML External Entity (XXE) vulnerability in Apache OpenNLP's\ndictionary parsing. The `DictionaryEntryPersistor` class and the public `Dictionary(InputStream)`\nconstructor create a SAX parser without enabling `FEATURE_SECURE_PROCESSING` or disabling DTD\nprocessing, so external entity resolution and DOCTYPE declarations remain fully enabled. An attacker\nwho can supply a crafted dictionary file \u2014 either directly or embedded [...]
- "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ "action_statement": "CVE-2026-40682 (CVSS 9.1) is an XML External Entity (XXE) vulnerability in Apache OpenNLP's\ndictionary parsing. The `DictionaryEntryPersistor` class and the public `Dictionary(InputStream)`\nconstructor create a SAX parser without enabling `FEATURE_SECURE_PROCESSING` or disabling DTD\nprocessing, so external entity resolution and DOCTYPE declarations remain fully enabled. An attacker\nwho can supply a crafted dictionary file \u2014 either directly or embedded [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-9.10.1,10.0.0."
},
{
"vulnerability": {
@@ -1208,8 +1210,8 @@
],
"status": "affected",
"timestamp": "2026-05-04T00:00:00Z",
- "action_statement": "CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue in Apache OpenNLP's\n`ExtensionLoader`. The `instantiateExtension(Class, String)` method loads a class named in a\nmodel archive's `manifest.properties` via `Class.forName()` and only performs its\n`isAssignableFrom` type check *after* the class has been loaded. Because `Class.forName()`\nruns the target class's static initializer at load time, an attacker who can supply a crafted\nmodel archiv [...]
- "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ "action_statement": "CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue in Apache OpenNLP's\n`ExtensionLoader`. The `instantiateExtension(Class, String)` method loads a class named in a\nmodel archive's `manifest.properties` via `Class.forName()` and only performs its\n`isAssignableFrom` type check *after* the class has been loaded. Because `Class.forName()`\nruns the target class's static initializer at load time, an attacker who can supply a crafted\nmodel archiv [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-9.10.1,10.0.0."
},
{
"vulnerability": {
@@ -1237,8 +1239,8 @@
],
"status": "affected",
"timestamp": "2026-05-04T00:00:00Z",
- "action_statement": "CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary\nmodel reader. The `AbstractModelReader` methods `getOutcomes()`, `getOutcomePatterns()` and\n`getPredicates()` read a 32-bit signed integer count field from a binary model stream and pass it\ndirectly to an array allocation without validating it. An attacker who can supply a crafted `.bin`\nmodel file with a count set to `Integer.MAX_VALUE` triggers an immediate `O [...]
- "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ "action_statement": "CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary\nmodel reader. The `AbstractModelReader` methods `getOutcomes()`, `getOutcomePatterns()` and\n`getPredicates()` read a 32-bit signed integer count field from a binary model stream and pass it\ndirectly to an array allocation without validating it. An attacker who can supply a crafted `.bin`\nmodel file with a count set to `Integer.MAX_VALUE` triggers an immediate `O [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-9.10.1,10.0.0."
},
{
"vulnerability": {
@@ -2176,6 +2178,618 @@
"justification": "vulnerable_code_not_in_execute_path",
"impact_statement": "GHSA-72hv-8253-57qq is a DoS vulnerability in the non-blocking (async) JSON parser API of jackson-core (NonBlockingByteArrayJsonParser), which bypasses the maxNumberLength constraint. Exploitation requires an application to use the async/non-blocking parser API (factory.createNonBlockingByteArrayParser()). Solr uses the standard synchronous Jackson parser to deserialize JSON from HTTP request bodies and internal data structures. Solr is built on Jetty with sync [...]
"status_notes": "Affected Apache Solr versions: 4.7.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2024-47561",
+ "aliases": [
+ "CVE-2023-39410"
+ ]
+ },
+ "products": [
+ {
+ "@id": "avro-1.9.2.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing\nan attacker-controlled Avro **schema** can instantiate arbitrary classes (affects avro < 1.11.4).\nCVE-2023-39410 is a memory-exhaustion / DoS issue when **deserializing untrusted Avro data** (affects\navro < 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.\n\nSolr is **not affected**:\n\n* **Solr does not use Apache Avro. [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-9.10.1."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2025-49128"
+ },
+ "products": [
+ {
+ "@id": "jackson-core-2.12.7.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2025-49128 can disclose adjacent buffer memory through the source snippet that jackson-core\nincludes in `JsonLocation` (e.g. surfaced in parse-error messages). It affects jackson-core < 2.13.0.\n\nSolr is **not affected**. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 \u2014 both\nwell past the 2.13.0 fix. The `2.12.7` copy a scanner flags is Hadoop's shaded jackson-core,\nreachable only via the optional Hadoop modules, which parse ad [...]
+ "status_notes": "Affected Apache Solr versions: 4.7.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "GHSA-r7wm-3cxj-wff9",
+ "aliases": [
+ "CVE-2025-52999"
+ ]
+ },
+ "products": [
+ {
+ "@id": "jackson-core-2.12.7.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "GHSA-r7wm-3cxj-wff9 is a `maxNumberLength` bypass in jackson-core's **async / non-blocking** parser\n(an incomplete fix for GHSA-72hv-8253-57qq; affects < 2.18.8 and 2.19.0\u20132.21.3). CVE-2025-52999 is a\n`StackOverflowError` when parsing **very deeply nested** input (affects < 2.15.0).\n\nSolr is **not affected**:\n\n* **The async parser is never used.** Solr deserializes JSON with the standard *synchronous* Jackson\n parser; it never calls the non-blockin [...]
+ "status_notes": "Affected Apache Solr versions: 4.7.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2025-53864"
+ },
+ "products": [
+ {
+ "@id": "nimbus-jose-jwt-9.37.2.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Nimbus JOSE + JWT library when\nparsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x < 9.37.4 and 10.0.x < 10.0.2).\n\nSolr is **not affected**. Solr's JWT authentication (the optional `jwt-auth` module, `JWTAuthPlugin`)\nparses and validates tokens exclusively with **jose4j** (`org.jose4j.*` \u2014 the plugin imports jose4j\nand does not reference `com.nimbusds` at all). N [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-10050"
+ },
+ "products": [
+ {
+ "@id": "jetty-security-10.0.26.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-10050 is a lossy-encoding flaw in Eclipse Jetty's **Digest authentication** implementation\n(in `jetty-security`), which can weaken Digest credential handling. It affects the Jetty branches\nSolr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12.1.10).\n\nSolr is **not affected**. Solr bundles `jetty-security` as part of the Jetty server stack, but it\ndoes not use Jetty's declarative security: it never installs [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-10051"
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.13"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.15"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.17"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.19"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.20"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.22"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.26"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@12.0.27"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.10.v20180503"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.11.v20180605"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.14.v20181114"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.19.v20190610"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.27.v20200227"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.34.v20201102"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.44.v20210927"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.48.v20220622"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.8.v20171121"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-10051 is an information-exposure bug in Jetty's `HttpConnection`: the `_trailers` field is\nnot reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request\ncan be observed via `getTrailers()` on a later request on the same connection. It has security impact\nonly for applications that **read HTTP trailers** (`request.getTrailers()`) and use them for logic or\nsecurity decisions.\n\nSolr is **not affected**. Solr doe [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-43869"
+ },
+ "products": [
+ {
+ "@id": "libthrift-0.15.0.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "impact_statement": "CVE-2026-43869 is a TLS hostname-verification weakness in Apache Thrift's\n`TSSLTransportFactory` (affects libthrift \u2264 0.22.0, fixed in 0.23.0): a client using Thrift's TLS\ntransport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on\nthat connection.\n\nSolr is **not affected** in any default or recommended configuration. `libthrift` is bundled only by\nthe optional, opt-in **`jaegertracer-configurator`** module (J [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-45205"
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.10.1"
+ },
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.11.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.12.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.7"
+ },
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.8.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.commons/commons-configuration2@2.9.0"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-45205 is a `StackOverflowError` (DoS) when Apache Commons Configuration parses YAML input\ncontaining reference cycles (affects 2.2 \u2013 2.14.x, fixed in 2.15.0).\n\nSolr is **not affected**. Solr uses `commons-configuration2` only transitively, via the optional\nHadoop integration (Kerberos / HDFS support), to load **administrator-supplied** Hadoop configuration\nfiles \u2014 not untrusted, externally-supplied YAML. No Solr request path feeds attack [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-46718"
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.27.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.32.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.33.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.34.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.35.0"
+ },
+ {
+ "@id": "pkg:maven/org.apache.calcite/calcite-core@1.37.0"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-46718 lets a **user-controlled Calcite model** load arbitrary classes, leading to code\nexecution (affects calcite-core 1.5.0 \u2013 1.41.x, fixed in 1.42.0). Exploitation requires the\napplication to let an attacker supply the Calcite *model* (the JSON schema/model definition that can\nname factory classes).\n\nSolr is **not affected**. Calcite is used only by the optional `sql` module (Parallel SQL, the `/sql`\nhandler). Solr constructs the Calcite s [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-50193",
+ "aliases": [
+ "CVE-2026-54514",
+ "CVE-2026-54515",
+ "CVE-2026-59889",
+ "CVE-2026-59888",
+ "GHSA-mhm7-754m-9p8w"
+ ]
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.10.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.10.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.11.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.2.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.3"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.4.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.14.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.15.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.16.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.17.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.18.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.20.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.3.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.5.4"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.5"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.6"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.8"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.9.3"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's s [...]
+ "status_notes": "Affected Apache Solr versions: 4.7.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-54512",
+ "aliases": [
+ "CVE-2026-54513"
+ ]
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.10.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.10.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.11.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.2.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.3"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.13.4.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.14.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.15.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.16.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.17.2"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.18.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.20.0"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.3.1"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.5.4"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.5"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.6"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.8"
+ },
+ {
+ "@id": "pkg:maven/com.fasterxml.jackson.core/jackson-databind@2.9.9.3"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's `PolymorphicTypeValidator` \u2014 via\ngeneric type parameters (54512) and via an array-subtype allowlist gap in\n`allowIfSubType` (54513) \u2014 that can let unexpected classes be instantiated during polymorphic\ndeserialization (affects 2.10.0\u20132.18.7 and 2.19.0\u20132.21.3).\n\nSolr is **not affected**. Both issues are only exploitable when an application enables **polymorphic\ndeserial [...]
+ "status_notes": "Affected Apache Solr versions: 4.7.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-56740",
+ "aliases": [
+ "CVE-2026-56741"
+ ]
+ },
+ "products": [
+ {
+ "@id": "jline-remote-telnet-3.9.0.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_present",
+ "impact_statement": "CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in **JLine's\nTelnet server** \u2014 unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values\n(56741) in the `jline-remote-telnet` Telnet daemon (affects < 3.30.14, and the 4.0.x / 4.1.x lines).\n\nSolr is **not affected**:\n\n* **The vulnerable component is not shipped or run.** Solr ships no `jline-remote-telnet` jar; the\n `3.9.0` coordinate a s [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-56745",
+ "aliases": [
+ "CVE-2026-55833",
+ "CVE-2026-55831",
+ "CVE-2026-56819",
+ "CVE-2026-59901"
+ ]
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.104.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.108.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.111.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.114.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.89.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.93.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.99.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.2.6.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.104.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.108.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.111.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.114.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.89.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.93.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.99.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.2.6.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-compression@4.2.6.Final"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u [...]
+ "status_notes": "Affected Apache Solr versions: 9.2.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-59899",
+ "aliases": [
+ "CVE-2026-56746",
+ "CVE-2026-59898",
+ "CVE-2026-59921",
+ "CVE-2026-59900"
+ ]
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.104.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.108.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.111.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.114.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.89.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.93.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.1.99.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http@4.2.6.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.104.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.108.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.111.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.114.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.89.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.93.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.1.99.Final"
+ },
+ {
+ "@id": "pkg:maven/io.netty/netty-codec-http2@4.2.6.Final"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handsha [...]
+ "status_notes": "Affected Apache Solr versions: 9.2.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-59949"
+ },
+ "products": [
+ {
+ "@id": "lz4-java-1.10.1.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-59949 (CVSS 6.5) is an out-of-bounds read in the `at.yawk.lz4:lz4-java` codec: the\nJNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that\npasses an invalid array reference or an out-of-range `off`/`len` to the native XXHash methods can\ncrash the JVM. It affects lz4-java \u2264 1.11.0 (fixed in 1.11.1). Exploitation requires an application\nto pass attacker-influenced array/offset/length values into thos [...]
+ "status_notes": "Affected Apache Solr versions: 9.0.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-6790"
+ },
+ "products": [
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.13"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.15"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.17"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.19"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.20"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.22"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@10.0.26"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@12.0.27"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.10.v20180503"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.11.v20180605"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.14.v20181114"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.19.v20190610"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.24.v20191120"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.27.v20200227"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.34.v20201102"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.44.v20210927"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.48.v20220622"
+ },
+ {
+ "@id": "pkg:maven/org.eclipse.jetty/jetty-server@9.4.8.v20171121"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-6790 is an input-validation gap in Jetty's HTTP/2 (and HTTP/3) request processing: Jetty\ndoes not require the `:authority` pseudo-header to match the `Host` header, so a single request can\ncarry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x\nthrough 10.0.26, 12.0.x through 12.0.34). It has security impact only for applications that **make\nsecurity-sensitive decisions based on the request host** \u2014 [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
+ },
+ {
+ "vulnerability": {
+ "name": "CVE-2026-8384"
+ },
+ "products": [
+ {
+ "@id": "jetty-util-10.0.26.jar"
+ }
+ ],
+ "status": "not_affected",
+ "timestamp": "2026-07-31T00:00:00Z",
+ "justification": "vulnerable_code_not_in_execute_path",
+ "impact_statement": "CVE-2026-8384 is a path-canonicalization flaw in Jetty's `URIUtil.canonicalPath()`: a semicolon\npath-parameter marker before dot-dot segments (e.g. `/public;/../admin/secret`) is not normalized,\nso a path-prefix authorization check can be bypassed. It is exploitable by applications that use\nJetty's `SecurityHandler.PathMapped`, or that make an authorization decision on a canonicalized path\nat a **different layer** than the one that ultimately dispatches the [...]
+ "status_notes": "Affected Apache Solr versions: 7.3.0-10.0.0."
}
]
}
\ No newline at end of file
diff --git a/output/solr.vex.json b/output/solr.vex.json
index 534f3f121..80e1904c1 100644
--- a/output/solr.vex.json
+++ b/output/solr.vex.json
@@ -7,7 +7,7 @@
"name": "solr",
"version": "SNAPSHOT",
"type": "application",
- "bom-ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "bom-ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
},
"vulnerabilities": [
@@ -23,7 +23,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -39,7 +39,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -55,7 +55,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -71,7 +71,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -87,7 +87,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -103,7 +103,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -119,7 +119,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -135,7 +135,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -151,7 +151,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -167,7 +167,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -183,7 +183,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -199,7 +199,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -215,7 +215,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -231,7 +231,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -247,7 +247,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -263,7 +263,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -279,7 +279,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -295,7 +295,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -311,7 +311,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -327,7 +327,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -343,7 +343,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -359,7 +359,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -375,7 +375,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -391,7 +391,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -407,7 +407,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -423,7 +423,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -439,7 +439,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -455,7 +455,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -471,7 +471,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -487,7 +487,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -503,7 +503,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -519,7 +519,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -535,7 +535,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -551,7 +551,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -567,7 +567,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -583,7 +583,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -599,7 +599,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -615,7 +615,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -631,7 +631,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -647,7 +647,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -663,7 +663,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -679,7 +679,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -695,7 +695,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -711,7 +711,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -727,7 +727,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -743,7 +743,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -759,7 +759,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -775,7 +775,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -791,7 +791,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -807,7 +807,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -823,7 +823,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -839,7 +839,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -855,7 +855,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -871,7 +871,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -887,7 +887,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -903,7 +903,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -919,7 +919,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -935,7 +935,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -951,7 +951,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -970,7 +970,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -986,7 +986,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1002,7 +1002,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1018,7 +1018,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1037,7 +1037,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1053,7 +1053,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1070,7 +1070,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1081,12 +1081,13 @@
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7254"
},
"analysis": {
- "state": "in_triage",
- "detail": "When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.\n\nCVE-2024-7254 affects all `protobuf-java` releases before 3.25.5 (per the upstream advisory the\nflaw was introduced at version 0, and is fixed in 3.25.5 / 4.27.5 / 4.28.2). Apache Solr has bundled\n`protobuf-java` (transitively, via Hadoop and ZooKeeper) since **Solr 4.4.0** (which shipped 2.4.0a),\nand e [...]
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.\n\nSolr is **not affected**. The crafted-message DoS requires an attacker to feed protobuf input to a\nparser, and Solr exposes no such path:\n\n* **Solr's own code never uses protobuf.** There is no `com.google.protobuf` usage anywhere in the\n Solr codebase, and Solr's client-facing APIs speak javabin, JSO [...]
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1103,7 +1104,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1120,7 +1121,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1137,7 +1138,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1154,7 +1155,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1171,7 +1172,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1188,7 +1189,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1204,11 +1205,11 @@
"workaround_available",
"update"
],
- "detail": "CVE-2026-40682 (CVSS 9.1) is an XML External Entity (XXE) vulnerability in Apache OpenNLP's\ndictionary parsing. The `DictionaryEntryPersistor` class and the public `Dictionary(InputStream)`\nconstructor create a SAX parser without enabling `FEATURE_SECURE_PROCESSING` or disabling DTD\nprocessing, so external entity resolution and DOCTYPE declarations remain fully enabled. An attacker\nwho can supply a crafted dictionary file \u2014 either directly or embedded in a mod [...]
+ "detail": "CVE-2026-40682 (CVSS 9.1) is an XML External Entity (XXE) vulnerability in Apache OpenNLP's\ndictionary parsing. The `DictionaryEntryPersistor` class and the public `Dictionary(InputStream)`\nconstructor create a SAX parser without enabling `FEATURE_SECURE_PROCESSING` or disabling DTD\nprocessing, so external entity resolution and DOCTYPE declarations remain fully enabled. An attacker\nwho can supply a crafted dictionary file \u2014 either directly or embedded in a mod [...]
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1224,11 +1225,11 @@
"workaround_available",
"update"
],
- "detail": "CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue in Apache OpenNLP's\n`ExtensionLoader`. The `instantiateExtension(Class, String)` method loads a class named in a\nmodel archive's `manifest.properties` via `Class.forName()` and only performs its\n`isAssignableFrom` type check *after* the class has been loaded. Because `Class.forName()`\nruns the target class's static initializer at load time, an attacker who can supply a crafted\nmodel archive can tr [...]
+ "detail": "CVE-2026-42027 (CVSS 9.8) is an arbitrary class instantiation issue in Apache OpenNLP's\n`ExtensionLoader`. The `instantiateExtension(Class, String)` method loads a class named in a\nmodel archive's `manifest.properties` via `Class.forName()` and only performs its\n`isAssignableFrom` type check *after* the class has been loaded. Because `Class.forName()`\nruns the target class's static initializer at load time, an attacker who can supply a crafted\nmodel archive can tr [...]
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1244,11 +1245,11 @@
"workaround_available",
"update"
],
- "detail": "CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary\nmodel reader. The `AbstractModelReader` methods `getOutcomes()`, `getOutcomePatterns()` and\n`getPredicates()` read a 32-bit signed integer count field from a binary model stream and pass it\ndirectly to an array allocation without validating it. An attacker who can supply a crafted `.bin`\nmodel file with a count set to `Integer.MAX_VALUE` triggers an immediate `OutOfMemo [...]
+ "detail": "CVE-2026-42440 (CVSS 7.5) is an out-of-memory denial-of-service issue in Apache OpenNLP's binary\nmodel reader. The `AbstractModelReader` methods `getOutcomes()`, `getOutcomePatterns()` and\n`getPredicates()` read a 32-bit signed integer count field from a binary model stream and pass it\ndirectly to an array allocation without validating it. An attacker who can supply a crafted `.bin`\nmodel file with a count set to `Integer.MAX_VALUE` triggers an immediate `OutOfMemo [...]
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1265,7 +1266,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1285,7 +1286,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1302,7 +1303,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1319,7 +1320,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1336,7 +1337,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1353,7 +1354,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1370,7 +1371,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1387,7 +1388,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1404,7 +1405,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1421,7 +1422,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1438,7 +1439,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1455,7 +1456,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1472,7 +1473,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1489,7 +1490,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1506,7 +1507,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1523,7 +1524,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1540,7 +1541,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1557,7 +1558,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1574,7 +1575,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1591,7 +1592,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1608,7 +1609,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1625,7 +1626,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1642,7 +1643,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1659,7 +1660,7 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
},
@@ -1676,7 +1677,585 @@
},
"affects": [
{
- "ref": "ec572863-4dd1-5f75-a901-ba21a0c46c39"
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2024-47561",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47561"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing\nan attacker-controlled Avro **schema** can instantiate arbitrary classes (affects avro < 1.11.4).\nCVE-2023-39410 is a memory-exhaustion / DoS issue when **deserializing untrusted Avro data** (affects\navro < 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.\n\nSolr is **not affected**:\n\n* **Solr does not use Apache Avro.** There [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2023-39410",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39410"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing\nan attacker-controlled Avro **schema** can instantiate arbitrary classes (affects avro < 1.11.4).\nCVE-2023-39410 is a memory-exhaustion / DoS issue when **deserializing untrusted Avro data** (affects\navro < 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.\n\nSolr is **not affected**:\n\n* **Solr does not use Apache Avro.** There [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2025-49128",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49128"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2025-49128 can disclose adjacent buffer memory through the source snippet that jackson-core\nincludes in `JsonLocation` (e.g. surfaced in parse-error messages). It affects jackson-core < 2.13.0.\n\nSolr is **not affected**. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 \u2014 both\nwell past the 2.13.0 fix. The `2.12.7` copy a scanner flags is Hadoop's shaded jackson-core,\nreachable only via the optional Hadoop modules, which parse administra [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "GHSA-r7wm-3cxj-wff9",
+ "source": {
+ "name": "GITHUB",
+ "url": "https://github.com/advisories/GHSA-r7wm-3cxj-wff9"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "GHSA-r7wm-3cxj-wff9 is a `maxNumberLength` bypass in jackson-core's **async / non-blocking** parser\n(an incomplete fix for GHSA-72hv-8253-57qq; affects < 2.18.8 and 2.19.0\u20132.21.3). CVE-2025-52999 is a\n`StackOverflowError` when parsing **very deeply nested** input (affects < 2.15.0).\n\nSolr is **not affected**:\n\n* **The async parser is never used.** Solr deserializes JSON with the standard *synchronous* Jackson\n parser; it never calls the non-blocking `NonBl [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2025-52999",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52999"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "GHSA-r7wm-3cxj-wff9 is a `maxNumberLength` bypass in jackson-core's **async / non-blocking** parser\n(an incomplete fix for GHSA-72hv-8253-57qq; affects < 2.18.8 and 2.19.0\u20132.21.3). CVE-2025-52999 is a\n`StackOverflowError` when parsing **very deeply nested** input (affects < 2.15.0).\n\nSolr is **not affected**:\n\n* **The async parser is never used.** Solr deserializes JSON with the standard *synchronous* Jackson\n parser; it never calls the non-blocking `NonBl [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2025-53864",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-53864"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Nimbus JOSE + JWT library when\nparsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x < 9.37.4 and 10.0.x < 10.0.2).\n\nSolr is **not affected**. Solr's JWT authentication (the optional `jwt-auth` module, `JWTAuthPlugin`)\nparses and validates tokens exclusively with **jose4j** (`org.jose4j.*` \u2014 the plugin imports jose4j\nand does not reference `com.nimbusds` at all). Nimbus JO [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-10050",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10050"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-10050 is a lossy-encoding flaw in Eclipse Jetty's **Digest authentication** implementation\n(in `jetty-security`), which can weaken Digest credential handling. It affects the Jetty branches\nSolr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12.1.10).\n\nSolr is **not affected**. Solr bundles `jetty-security` as part of the Jetty server stack, but it\ndoes not use Jetty's declarative security: it never installs a Jetty [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-10051",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-10051"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-10051 is an information-exposure bug in Jetty's `HttpConnection`: the `_trailers` field is\nnot reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request\ncan be observed via `getTrailers()` on a later request on the same connection. It has security impact\nonly for applications that **read HTTP trailers** (`request.getTrailers()`) and use them for logic or\nsecurity decisions.\n\nSolr is **not affected**. Solr does not re [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-43869",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43869"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "requires_configuration",
+ "detail": "CVE-2026-43869 is a TLS hostname-verification weakness in Apache Thrift's\n`TSSLTransportFactory` (affects libthrift \u2264 0.22.0, fixed in 0.23.0): a client using Thrift's TLS\ntransport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on\nthat connection.\n\nSolr is **not affected** in any default or recommended configuration. `libthrift` is bundled only by\nthe optional, opt-in **`jaegertracer-configurator`** module (Jaeger di [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-45205",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45205"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-45205 is a `StackOverflowError` (DoS) when Apache Commons Configuration parses YAML input\ncontaining reference cycles (affects 2.2 \u2013 2.14.x, fixed in 2.15.0).\n\nSolr is **not affected**. Solr uses `commons-configuration2` only transitively, via the optional\nHadoop integration (Kerberos / HDFS support), to load **administrator-supplied** Hadoop configuration\nfiles \u2014 not untrusted, externally-supplied YAML. No Solr request path feeds attacker-contr [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-46718",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46718"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-46718 lets a **user-controlled Calcite model** load arbitrary classes, leading to code\nexecution (affects calcite-core 1.5.0 \u2013 1.41.x, fixed in 1.42.0). Exploitation requires the\napplication to let an attacker supply the Calcite *model* (the JSON schema/model definition that can\nname factory classes).\n\nSolr is **not affected**. Calcite is used only by the optional `sql` module (Parallel SQL, the `/sql`\nhandler). Solr constructs the Calcite schema/mo [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-50193",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-50193"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-54514",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54514"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-54515",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54515"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59889",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59889"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59888",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59888"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "GHSA-mhm7-754m-9p8w",
+ "source": {
+ "name": "GITHUB",
+ "url": "https://github.com/advisories/GHSA-mhm7-754m-9p8w"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "Four jackson-databind issues, in two groups:\n\n* **Only the Hadoop-shaded old copy is affected.** CVE-2026-50193 (StackOverflow on `toString()` of a\n deeply-nested `JsonNode`, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when\n deserializing into `InetSocketAddress`, fixed 2.18.8 / 2.21.4) do not affect Solr's own\n jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 \u2014 both patched). The `2.12.7.1` a scanner\n flags is Hadoop's shaded co [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-54512",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54512"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's `PolymorphicTypeValidator` \u2014 via\ngeneric type parameters (54512) and via an array-subtype allowlist gap in\n`allowIfSubType` (54513) \u2014 that can let unexpected classes be instantiated during polymorphic\ndeserialization (affects 2.10.0\u20132.18.7 and 2.19.0\u20132.21.3).\n\nSolr is **not affected**. Both issues are only exploitable when an application enables **polymorphic\ndeserialization* [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-54513",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54513"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's `PolymorphicTypeValidator` \u2014 via\ngeneric type parameters (54512) and via an array-subtype allowlist gap in\n`allowIfSubType` (54513) \u2014 that can let unexpected classes be instantiated during polymorphic\ndeserialization (affects 2.10.0\u20132.18.7 and 2.19.0\u20132.21.3).\n\nSolr is **not affected**. Both issues are only exploitable when an application enables **polymorphic\ndeserialization* [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-56740",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56740"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_present",
+ "detail": "CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in **JLine's\nTelnet server** \u2014 unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values\n(56741) in the `jline-remote-telnet` Telnet daemon (affects < 3.30.14, and the 4.0.x / 4.1.x lines).\n\nSolr is **not affected**:\n\n* **The vulnerable component is not shipped or run.** Solr ships no `jline-remote-telnet` jar; the\n `3.9.0` coordinate a scanner r [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-56741",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56741"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_present",
+ "detail": "CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in **JLine's\nTelnet server** \u2014 unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values\n(56741) in the `jline-remote-telnet` Telnet daemon (affects < 3.30.14, and the 4.0.x / 4.1.x lines).\n\nSolr is **not affected**:\n\n* **The vulnerable component is not shipped or run.** Solr ships no `jline-remote-telnet` jar; the\n `3.9.0` coordinate a scanner r [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-56745",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56745"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u2014 inf [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-55833",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-55833"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u2014 inf [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-55831",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-55831"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u2014 inf [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-56819",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56819"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u2014 inf [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59901",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59901"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths\n(all affect Netty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 \u2014 the **SPDY** codec (`SpdyHttpDecoder` and SPDY\n header/settings handling) in `netty-codec-http`.\n* CVE-2026-56819 \u2014 server-side **HTTP/2 decompression** ByteBuf reference leak in `netty-codec-http2`.\n* CVE-2026-59901 \u2014 inf [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59899",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59899"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handshaker miss [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-56746",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56746"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handshaker miss [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59898",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59898"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handshaker miss [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59921",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59921"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handshaker miss [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59900",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59900"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect\nNetty < 4.1.136 and 4.2.0\u20134.2.15, fixed in 4.1.136 / 4.2.16):\n\n* CVE-2026-59899 \u2014 unbounded per-connection queue growth in `HttpContentEncoder` via HTTP/1.1\n pipelining (server response encoding).\n* CVE-2026-56746 \u2014 CORS short-circuit failure / security-control bypass (server CORS handler).\n* CVE-2026-59898 \u2014 WebSocket V07/V08 handshaker miss [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-59949",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-59949"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-59949 (CVSS 6.5) is an out-of-bounds read in the `at.yawk.lz4:lz4-java` codec: the\nJNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that\npasses an invalid array reference or an out-of-range `off`/`len` to the native XXHash methods can\ncrash the JVM. It affects lz4-java \u2264 1.11.0 (fixed in 1.11.1). Exploitation requires an application\nto pass attacker-influenced array/offset/length values into those XXHash [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-6790",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-6790"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-6790 is an input-validation gap in Jetty's HTTP/2 (and HTTP/3) request processing: Jetty\ndoes not require the `:authority` pseudo-header to match the `Host` header, so a single request can\ncarry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x\nthrough 10.0.26, 12.0.x through 12.0.34). It has security impact only for applications that **make\nsecurity-sensitive decisions based on the request host** \u2014 host-bas [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
+ }
+ ]
+ },
+ {
+ "id": "CVE-2026-8384",
+ "source": {
+ "name": "NVD",
+ "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-8384"
+ },
+ "analysis": {
+ "state": "not_affected",
+ "justification": "code_not_reachable",
+ "detail": "CVE-2026-8384 is a path-canonicalization flaw in Jetty's `URIUtil.canonicalPath()`: a semicolon\npath-parameter marker before dot-dot segments (e.g. `/public;/../admin/secret`) is not normalized,\nso a path-prefix authorization check can be bypassed. It is exploitable by applications that use\nJetty's `SecurityHandler.PathMapped`, or that make an authorization decision on a canonicalized path\nat a **different layer** than the one that ultimately dispatches the request [...]
+ },
+ "affects": [
+ {
+ "ref": "a883972a-5b79-56b7-bb94-719f999968d0"
}
]
}
diff --git a/output/vex.html b/output/vex.html
index ab798510d..70f1968cb 100644
--- a/output/vex.html
+++ b/output/vex.html
@@ -142,6 +142,531 @@
<h1>Apache Solr VEX</h1>
<p><a href="/security-dependency-cves.html">← Back to the dependency CVE table</a></p>
+ <article id="cve-2026-8384" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-8384">CVE-2026-8384</a>, Eclipse Jetty: non-canonical URL paths in URIUtil.canonicalPath (authorization bypass)</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-8384 is a path-canonicalization flaw in Jetty's <code>URIUtil.canonicalPath()</code>: a semicolon
+path-parameter marker before dot-dot segments (e.g. <code>/public;/../admin/secret</code>) is not normalized,
+so a path-prefix authorization check can be bypassed. It is exploitable by applications that use
+Jetty's <code>SecurityHandler.PathMapped</code>, or that make an authorization decision on a canonicalized path
+at a <strong>different layer</strong> than the one that ultimately dispatches the request (the classic
+canonicalization <em>desync</em>).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>No desync between authorization and dispatch.</strong> <code>HttpSolrCall</code> computes the request path once
+ (<code>ServletUtils.getPathAfterContext()</code>), and uses that single value for <em>both</em> request routing
+ (<code>getPath()</code>) and authorization (<code>getAuthCtx()</code> builds its <code>AuthorizationContext</code> resource from the
+ same <code>getPath()</code>). <code>RuleBasedAuthorizationPlugin</code> therefore evaluates exactly the path that Solr
+ dispatches — there is no window in which authorization sees one path while a different path is
+ served, which is the precondition this CVE requires.</li>
+<li><strong>Path parameters are already stripped.</strong> Solr derives the path from <code>getServletPath()</code> +
+ <code>getPathInfo()</code>, which per the Servlet specification have path parameters (the <code>;…</code> segments this
+ bug abuses) removed by the container before Solr ever sees the path.</li>
+<li>Solr uses neither Jetty's <code>SecurityHandler.PathMapped</code> nor <code>URIUtil.canonicalPath()</code> directly.</li>
+</ul>
+<p>So even on an affected Jetty, the mis-canonicalization cannot produce an authorization bypass in
+Solr, because Solr's authorization and dispatch are driven by the same, single path value.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-8384">CVE-2026-8384</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-6790" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-6790">CVE-2026-6790</a>, Eclipse Jetty: HTTP/2 :authority vs Host header confusion</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-6790 is an input-validation gap in Jetty's HTTP/2 (and HTTP/3) request processing: Jetty
+does not require the <code>:authority</code> pseudo-header to match the <code>Host</code> header, so a single request can
+carry two conflicting host interpretations. It affects the Jetty branches Solr ships (9.4.x, 10.0.x
+through 10.0.26, 12.0.x through 12.0.34). It has security impact only for applications that <strong>make
+security-sensitive decisions based on the request host</strong> — host-based access control, virtual-host
+isolation, multi-tenant routing, or host-derived redirect URLs.</p>
+<p>Solr is <strong>not affected</strong>. Solr does none of those things: it does not perform host-based access
+control or virtual-host/multi-tenant isolation, its authentication and authorization
+(<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code> framework) never key on the <code>Host</code>/<code>:authority</code>
+value, and it does not build security-sensitive redirects from the request host. With no
+host-dependent security decision, the host-confusion has no exploitable consequence in Solr.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-6790">CVE-2026-6790</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-59949" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59949">CVE-2026-59949</a>, lz4-java: out-of-bounds read via invalid arguments to native XXHash</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-59949 (CVSS 6.5) is an out-of-bounds read in the <code>at.yawk.lz4:lz4-java</code> codec: the
+JNI-based XXHash implementations insufficiently validate their byte-array arguments, so a caller that
+passes an invalid array reference or an out-of-range <code>off</code>/<code>len</code> to the native XXHash methods can
+crash the JVM. It affects lz4-java ≤ 1.11.0 (fixed in 1.11.1). Exploitation requires an application
+to pass attacker-influenced array/offset/length values into those XXHash APIs.</p>
+<p>Solr is <strong>not affected</strong>. <code>lz4-java</code> is bundled only by the optional <code>cross-dc</code> module, where it is
+used by the embedded Apache Kafka client for LZ4 compression / checksums of cross-datacenter
+replication messages. Kafka calls the XXHash APIs with its own internally-managed, validated buffers
+and offsets — it does not forward attacker-controlled <code>off</code>/<code>len</code> values into the native methods —
+and the replication stream flows through an operator-controlled Kafka pipeline, not untrusted
+external input. The <code>cross-dc</code> module is not part of a default Solr installation, and no Solr request
+path reaches the vulnerable XXHash argument handling.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59949">CVE-2026-59949</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-59899" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59899">CVE-2026-59899</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56746">CVE-2026-56746</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59898">CVE-2026-59898</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59921">CVE-2026-59921</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59900">CVE-2026-59900</a>, Netty codec-http/http2: server-side HTTP handling issues (DoS, C [...]
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.2.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>These five Netty issues live in server-side HTTP handling or the outbound request encoder (all affect
+Netty < 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-59899 — unbounded per-connection queue growth in <code>HttpContentEncoder</code> via HTTP/1.1
+ pipelining (server response encoding).</li>
+<li>CVE-2026-56746 — CORS short-circuit failure / security-control bypass (server CORS handler).</li>
+<li>CVE-2026-59898 — WebSocket V07/V08 handshaker missing Connection/Upgrade validation (server).</li>
+<li>CVE-2026-59921 — CRLF injection via multipart filename in the outbound <code>HttpPostRequestEncoder</code>.</li>
+<li>CVE-2026-59900 — Host-header de-duplication gap in HTTP/2→HTTP/1.x translation (server/proxy).</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty is used strictly as a <strong>client</strong>. Solr's HTTP server is Jetty:
+Solr never runs a Netty HTTP server, CORS handler, WebSocket server, or HTTP/2→1 proxy, and never
+uses Netty's multipart request encoder, so none of these code paths are reachable.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59899">CVE-2026-59899</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56746">CVE-2026-56746</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59898">CVE-2026-59898</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59921">CVE-2026-59921</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59900">CVE-2026-59900</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-56745" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56745">CVE-2026-56745</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55833">CVE-2026-55833</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55831">CVE-2026-55831</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56819">CVE-2026-56819</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59901">CVE-2026-59901</a>, Netty codec: SPDY / HTTP2-decompression / Bzip2 denial-of-servic [...]
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.2.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>These five Netty issues are resource-exhaustion / DoS bugs in server- and decoder-side code paths
+(all affect Netty < 4.1.136 and 4.2.0–4.2.15, fixed in 4.1.136 / 4.2.16):</p>
+<ul>
+<li>CVE-2026-56745, CVE-2026-55833, CVE-2026-55831 — the <strong>SPDY</strong> codec (<code>SpdyHttpDecoder</code> and SPDY
+ header/settings handling) in <code>netty-codec-http</code>.</li>
+<li>CVE-2026-56819 — server-side <strong>HTTP/2 decompression</strong> ByteBuf reference leak in <code>netty-codec-http2</code>.</li>
+<li>CVE-2026-59901 — infinite loop in the <strong>Bzip2</strong> decoder in <code>netty-codec-compression</code>.</li>
+</ul>
+<p>Solr is <strong>not affected</strong>. Solr bundles Netty only via the optional OpenTelemetry (OTLP) exporter and
+the ZooKeeper client, where Netty acts strictly as a <strong>client</strong>. Solr's HTTP server is Jetty, not
+Netty: Solr never runs a Netty HTTP/HTTP2/SPDY server, never enables the SPDY codec, and never feeds
+attacker-controlled compressed (bzip2) streams through Netty. The vulnerable server/decoder code
+paths are therefore unreachable — the same reasoning as CVE-2026-33870 / CVE-2026-33871.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56745">CVE-2026-56745</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55833">CVE-2026-55833</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-55831">CVE-2026-55831</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56819">CVE-2026-56819</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59901">CVE-2026-59901</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-56740" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56740">CVE-2026-56740</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56741">CVE-2026-56741</a>, JLine: unauthenticated remote DoS in the Telnet server</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-56740 and CVE-2026-56741 are unauthenticated remote denial-of-service issues in <strong>JLine's
+Telnet server</strong> — unbounded NEW-ENVIRON variables (56740) and unbounded NAWS terminal-geometry values
+(56741) in the <code>jline-remote-telnet</code> Telnet daemon (affects < 3.30.14, and the 4.0.x / 4.1.x lines).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The vulnerable component is not shipped or run.</strong> Solr ships no <code>jline-remote-telnet</code> jar; the
+ <code>3.9.0</code> coordinate a scanner reports comes only from a dependency reference embedded in the bundled
+ <code>zookeeper-3.9.5</code> jar's metadata. Solr never starts a JLine Telnet server (<code>Telnetd</code>).</li>
+<li>JLine is used, at most, for the local interactive <code>bin/solr</code> CLI terminal — a <code>LineReader</code> on the
+ operator's own console, not a network-listening Telnet daemon — so nothing accepts remote Telnet
+ connections that the vulnerable NAWS/NEW-ENVIRON parsing could act on.</li>
+</ul>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56740">CVE-2026-56740</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-56741">CVE-2026-56741</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-54512" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54512">CVE-2026-54512</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54513">CVE-2026-54513</a>, jackson-databind: PolymorphicTypeValidator allowlist bypasses (unsafe deserialization)</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 4.7.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-54512 and CVE-2026-54513 are bypasses of jackson-databind's <code>PolymorphicTypeValidator</code> — via
+generic type parameters (54512) and via an array-subtype allowlist gap in
+<code>allowIfSubType</code> (54513) — that can let unexpected classes be instantiated during polymorphic
+deserialization (affects 2.10.0–2.18.7 and 2.19.0–2.21.3).</p>
+<p>Solr is <strong>not affected</strong>. Both issues are only exploitable when an application enables <strong>polymorphic
+deserialization</strong> — default typing (<code>activateDefaultTyping</code>), <code>@JsonTypeInfo</code>, or a
+<code>BasicPolymorphicTypeValidator</code> allowlist — and then deserializes attacker-controlled JSON through it.
+Solr does none of this: it maps request JSON to fixed, known target types and never enables default
+typing or polymorphic deserialization of untrusted input, so the <code>PolymorphicTypeValidator</code> code path
+these CVEs target is never exercised. (The <code>2.12.7.1</code> copy a scanner flags is Hadoop's shaded
+jackson-databind; Solr's own is 2.18.0 in current 9.x and 2.22.0 in 9.11.)</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54512">CVE-2026-54512</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54513">CVE-2026-54513</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-50193" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-50193">CVE-2026-50193</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54514">CVE-2026-54514</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54515">CVE-2026-54515</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59889">CVE-2026-59889</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59888">CVE-2026-59888</a>, <a href="https://github.com/advisories/GHSA-mhm7-754m-9p8w">GHSA [...]
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 4.7.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>Four jackson-databind issues, in two groups:</p>
+<ul>
+<li><strong>Only the Hadoop-shaded old copy is affected.</strong> CVE-2026-50193 (StackOverflow on <code>toString()</code> of a
+ deeply-nested <code>JsonNode</code>, fixed 2.14.0) and CVE-2026-54514 (eager DNS resolution / SSRF when
+ deserializing into <code>InetSocketAddress</code>, fixed 2.18.8 / 2.21.4) do not affect Solr's own
+ jackson-databind (2.18.0 in current 9.x, 2.22.0 in 9.11 — both patched). The <code>2.12.7.1</code> a scanner
+ flags is Hadoop's shaded copy, reachable only through the optional Hadoop modules, which process
+ administrator-supplied configuration rather than untrusted external JSON.</li>
+<li><strong>Require Jackson features Solr does not use.</strong> CVE-2026-54515 (case-insensitive deserialization
+ bypassing per-property <code>@JsonIgnoreProperties</code>), CVE-2026-59889 (<code>@JsonView</code> bypass for
+ <code>@JsonUnwrapped</code> container properties), CVE-2026-59888 (<code>@JsonIgnore</code> on a Record property bypassed
+ via a <code>PropertyNamingStrategy</code>), and GHSA-mhm7-754m-9p8w (<code>@JsonView</code> bypass for creator properties
+ with <code>@JsonTypeInfo(include = As.EXTERNAL_PROPERTY)</code>) can reach Solr's own jackson-databind, but
+ only when an application relies on those annotation-based mechanisms — case-insensitive property
+ mapping, <code>@JsonView</code>, <code>@JsonUnwrapped</code>, <code>@JsonIgnore</code> on records, or <code>@JsonTypeInfo</code> external-property
+ polymorphism — to restrict which fields untrusted input may set. Solr uses none of them: it maps
+ request JSON to fixed, known types and never applies <code>@JsonView</code>/<code>@JsonIgnore</code>-based deserialization
+ filtering or polymorphic typing to untrusted input, so these bypasses have nothing to bypass.</li>
+</ul>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-50193">CVE-2026-50193</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54514">CVE-2026-54514</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-54515">CVE-2026-54515</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59889">CVE-2026-59889</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-59888">CVE-2026-59888</a>, <a href="https://github.com/advisories/GHSA-mhm7-754m-9p8w">GHSA-mhm7 [...]
+ </ul>
+ </article>
+ <article id="cve-2026-46718" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-46718">CVE-2026-46718</a>, Apache Calcite: arbitrary class loading via a user-controlled model</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-46718 lets a <strong>user-controlled Calcite model</strong> load arbitrary classes, leading to code
+execution (affects calcite-core 1.5.0 – 1.41.x, fixed in 1.42.0). Exploitation requires the
+application to let an attacker supply the Calcite <em>model</em> (the JSON schema/model definition that can
+name factory classes).</p>
+<p>Solr is <strong>not affected</strong>. Calcite is used only by the optional <code>sql</code> module (Parallel SQL, the <code>/sql</code>
+handler). Solr constructs the Calcite schema/model <strong>server-side</strong> from the target collection; users
+submit only a SQL statement, never a Calcite model or schema-factory definition. There is no request
+path through which an attacker can supply a Calcite model, so the arbitrary-class-loading vector is
+never reached.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-46718">CVE-2026-46718</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-45205" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-45205">CVE-2026-45205</a>, Apache Commons Configuration: StackOverflowError for YAML input with cycles</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-45205 is a <code>StackOverflowError</code> (DoS) when Apache Commons Configuration parses YAML input
+containing reference cycles (affects 2.2 – 2.14.x, fixed in 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>. Solr uses <code>commons-configuration2</code> only transitively, via the optional
+Hadoop integration (Kerberos / HDFS support), to load <strong>administrator-supplied</strong> Hadoop configuration
+files — not untrusted, externally-supplied YAML. No Solr request path feeds attacker-controlled YAML
+to Commons Configuration, so the cyclic-YAML parser cannot be driven by an adversary. (This matches
+the existing assessment of the other Commons Configuration CVEs in Solr.)</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-45205">CVE-2026-45205</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-43869" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-43869">CVE-2026-43869</a>, Apache Thrift (Java): TLS hostname verification in TSSLTransportFactory</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-43869 is a TLS hostname-verification weakness in Apache Thrift's
+<code>TSSLTransportFactory</code> (affects libthrift ≤ 0.22.0, fixed in 0.23.0): a client using Thrift's TLS
+transport may not properly verify the server certificate's hostname, enabling a man-in-the-middle on
+that connection.</p>
+<p>Solr is <strong>not affected</strong> in any default or recommended configuration. <code>libthrift</code> is bundled only by
+the optional, opt-in <strong><code>jaegertracer-configurator</code></strong> module (Jaeger distributed-tracing exporter) —
+it is not part of a default Solr install, and Solr does not use Thrift's TLS transport anywhere else.
+Even when Jaeger tracing is enabled, Solr exports spans to an <strong>operator-configured</strong> Jaeger backend
+(a trusted, first-party collector), not to an untrusted remote host, so there is no untrusted TLS
+peer for the missing hostname check to expose. The issue is only relevant to an operator who both
+enables Jaeger tracing and deliberately points it at an untrusted TLS endpoint.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-43869">CVE-2026-43869</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-10051" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10051">CVE-2026-10051</a>, Eclipse Jetty: HTTP/1.1 request trailers leak across keep-alive requests</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-10051 is an information-exposure bug in Jetty's <code>HttpConnection</code>: the <code>_trailers</code> field is
+not reset between requests on an HTTP/1.1 keep-alive connection, so trailer fields from one request
+can be observed via <code>getTrailers()</code> on a later request on the same connection. It has security impact
+only for applications that <strong>read HTTP trailers</strong> (<code>request.getTrailers()</code>) and use them for logic or
+security decisions.</p>
+<p>Solr is <strong>not affected</strong>. Solr does not read HTTP request trailers anywhere — there is no
+<code>getTrailers()</code> / trailer-field usage in the Solr codebase — so stale trailer state on a pooled
+connection is never observed by Solr and cannot influence request handling or authorization. The
+affected range spans the releases whose bundled Jetty is in an affected branch (Solr 7.3.0 – 10.0.0).</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10051">CVE-2026-10051</a></li>
+ </ul>
+ </article>
+ <article id="cve-2026-10050" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10050">CVE-2026-10050</a>, Eclipse Jetty: Digest authentication lossy encoding</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2026-10050 is a lossy-encoding flaw in Eclipse Jetty's <strong>Digest authentication</strong> implementation
+(in <code>jetty-security</code>), which can weaken Digest credential handling. It affects the Jetty branches
+Solr ships (10.0.x through 10.0.30, and 12.0.x through 12.0.35; fixed in 10.0.31 / 12.0.36 / 12.1.10).</p>
+<p>Solr is <strong>not affected</strong>. Solr bundles <code>jetty-security</code> as part of the Jetty server stack, but it
+does not use Jetty's declarative security: it never installs a Jetty <code>SecurityHandler</code> /
+<code>ConstraintSecurityHandler</code> and never configures a Jetty <code>Authenticator</code> (Digest or otherwise). Solr
+authenticates requests in its own servlet filter (<code>SolrDispatchFilter</code> / the <code>AuthenticationPlugin</code>
+framework — Basic, JWT, Kerberos, PKI, etc.), so Jetty's Digest-authentication code path — the code
+this CVE affects — is never invoked. The affected range spans the releases whose bundled Jetty is in
+an affected branch (Solr 7.3.0 – 10.0.0).</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-10050">CVE-2026-10050</a></li>
+ </ul>
+ </article>
+ <article id="cve-2025-53864" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-53864">CVE-2025-53864</a>, Nimbus JOSE + JWT: uncontrolled recursion (DoS) parsing crafted JOSE objects</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2025-53864 is an uncontrolled-recursion denial-of-service in the Nimbus JOSE + JWT library when
+parsing a maliciously crafted, deeply-nested JOSE object (affects 9.37.x < 9.37.4 and 10.0.x < 10.0.2).</p>
+<p>Solr is <strong>not affected</strong>. Solr's JWT authentication (the optional <code>jwt-auth</code> module, <code>JWTAuthPlugin</code>)
+parses and validates tokens exclusively with <strong>jose4j</strong> (<code>org.jose4j.*</code> — the plugin imports jose4j
+and does not reference <code>com.nimbusds</code> at all). Nimbus JOSE + JWT is not on Solr's JWT-processing code
+path; it appears only as a transitive/declared reference and is never invoked to parse an incoming
+token, so the vulnerable recursive parser cannot be reached by an attacker-supplied JWT.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-53864">CVE-2025-53864</a></li>
+ </ul>
+ </article>
+ <article id="cve-2025-52999" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://github.com/advisories/GHSA-r7wm-3cxj-wff9">GHSA-r7wm-3cxj-wff9</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-52999">CVE-2025-52999</a>, jackson-core: async-parser number-length bypass and deep-nesting StackOverflow (DoS)</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 4.7.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>GHSA-r7wm-3cxj-wff9 is a <code>maxNumberLength</code> bypass in jackson-core's <strong>async / non-blocking</strong> parser
+(an incomplete fix for GHSA-72hv-8253-57qq; affects < 2.18.8 and 2.19.0–2.21.3). CVE-2025-52999 is a
+<code>StackOverflowError</code> when parsing <strong>very deeply nested</strong> input (affects < 2.15.0).</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>The async parser is never used.</strong> Solr deserializes JSON with the standard <em>synchronous</em> Jackson
+ parser; it never calls the non-blocking <code>NonBlockingByteArrayParser</code> API, so the async-only
+ <code>maxNumberLength</code> bypass (GHSA-r7wm) is unreachable — as already assessed for GHSA-72hv-8253-57qq.</li>
+<li><strong>Solr's own jackson-core is patched.</strong> The bundled jackson-core is 2.18.0 in current 9.x and
+ 2.22.0 in 9.11 — both fixed for the deep-nesting StackOverflow (fixed in 2.15.0). The <code>2.12.7</code>
+ copy a scanner flags is Hadoop's <strong>shaded</strong> jackson, reachable only through the optional Hadoop
+ modules, which parse administrator-supplied configuration rather than untrusted external JSON.</li>
+</ul>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://github.com/advisories/GHSA-r7wm-3cxj-wff9">GHSA-r7wm-3cxj-wff9</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-52999">CVE-2025-52999</a></li>
+ </ul>
+ </article>
+ <article id="cve-2025-49128" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-49128">CVE-2025-49128</a>, jackson-core: memory disclosure via source snippet in JsonLocation error messages</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 4.7.0-10.0.0</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2025-49128 can disclose adjacent buffer memory through the source snippet that jackson-core
+includes in <code>JsonLocation</code> (e.g. surfaced in parse-error messages). It affects jackson-core < 2.13.0.</p>
+<p>Solr is <strong>not affected</strong>. Solr's own jackson-core is 2.18.0 in current 9.x and 2.22.0 in 9.11 — both
+well past the 2.13.0 fix. The <code>2.12.7</code> copy a scanner flags is Hadoop's shaded jackson-core,
+reachable only via the optional Hadoop modules, which parse administrator-supplied configuration
+rather than untrusted external JSON, and whose parse errors are not returned to remote clients.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-49128">CVE-2025-49128</a></li>
+ </ul>
+ </article>
+ <article id="cve-2024-47561" class="post panel radius">
+ <header class="post-header">
+ <h3 class="title"><a href="https://nvd.nist.gov/vuln/detail/CVE-2024-47561">CVE-2024-47561</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-39410">CVE-2023-39410</a>, Apache Avro (Java): RCE reading a crafted schema / DoS deserializing untrusted data</h3>
+ <div class="panel callout">
+ <p class="subheader">
+ <strong>Status:</strong>
+ <span class="cdx-not-affected">not_affected</span>
+ </p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 9.0.0-9.10.1</p>
+ </div>
+ </header>
+
+ <h4>Description</h4>
+ <p>CVE-2024-47561 (critical) is an arbitrary-code-execution issue in the Apache Avro Java SDK: parsing
+an attacker-controlled Avro <strong>schema</strong> can instantiate arbitrary classes (affects avro < 1.11.4).
+CVE-2023-39410 is a memory-exhaustion / DoS issue when <strong>deserializing untrusted Avro data</strong> (affects
+avro < 1.11.3). Both require the application to feed attacker-controlled Avro input to the SDK.</p>
+<p>Solr is <strong>not affected</strong>:</p>
+<ul>
+<li><strong>Solr does not use Apache Avro.</strong> There is no <code>org.apache.avro</code> usage anywhere in the Solr
+ codebase, and Solr ships no standalone <code>avro-*.jar</code>. Avro appears only as an embedded/transitive
+ artifact of the optional Hadoop integration (the <code>hdfs</code> / <code>hadoop-auth</code> modules, which are not part
+ of a default install).</li>
+<li><strong>The vulnerable entry points are never reached.</strong> Solr never parses an externally-supplied Avro
+ schema and never deserializes untrusted Avro data — the only code that pulls Avro in is Hadoop's
+ own internal machinery, driven by administrator-supplied configuration, not by untrusted request
+ input.</li>
+</ul>
+<p>The affected range covers the 9.x line, where the optional Hadoop modules transitively carry Avro
+1.9.2; Solr's own code path never invokes it.</p>
+
+ <h4>References</h4>
+ <ul>
+ <li>CVE: <a href="https://nvd.nist.gov/vuln/detail/CVE-2024-47561">CVE-2024-47561</a>, <a href="https://nvd.nist.gov/vuln/detail/CVE-2023-39410">CVE-2023-39410</a></li>
+ </ul>
+ </article>
<article id="ghsa-72hv-8253-57qq" class="post panel radius">
<header class="post-header">
<h3 class="title"><a href="https://github.com/advisories/GHSA-72hv-8253-57qq">GHSA-72hv-8253-57qq</a>, Jackson-core: async (non-blocking) parser bypasses maxNumberLength (DoS)</h3>
@@ -1305,7 +1830,7 @@ affected in a supported (authenticated) configuration throughout that range.</p>
<strong>Status:</strong>
<span class="cdx-exploitable">exploitable</span>
</p>
- <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-9.10.1,10.0.0</p>
</div>
</header>
@@ -1318,9 +1843,9 @@ model file with a count set to <code>Integer.MAX_VALUE</code> triggers an immedi
model deserialization, before any substantial data is consumed.</p>
<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP 2.5.9 (and
-3.0.0-M3), and backported to the end-of-life 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these
-validate the count against an upper bound (default 10,000,000, configurable via the
-<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating.</p>
+3.0.0-M3), which validate the count against an upper bound (default 10,000,000, configurable via the
+<code>OPENNLP_MAX_ENTRIES</code> system property) before allocating, and backported to the 1.9.x line as
+<code>opennlp-tools-1.9.5</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">¶</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable model-loading code path becomes reachable when:</p>
@@ -1337,12 +1862,14 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9. Solr has bundled OpenNLP (transitively,
-via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so every release from 7.3.0 through 10.0.0 ships an
-affected version (1.8.3 through 2.5.6). The affected range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fixed in Solr 9.11, which bundles the patched <code>opennlp-tools</code> 1.9.5, and in Solr 10.1, which upgrades
-the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9. Solr 10.0 remains affected (it ships
-OpenNLP 2.5.6).</p>
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p>
<h4>References</h4>
<ul>
@@ -1357,7 +1884,7 @@ OpenNLP 2.5.6).</p>
<strong>Status:</strong>
<span class="cdx-exploitable">exploitable</span>
</p>
- <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-9.10.1,10.0.0</p>
</div>
</header>
@@ -1370,8 +1897,9 @@ runs the target class's static initializer at load time, an attacker who can sup
model archive can trigger the static initializer of any class on the classpath (e.g. one that
performs a JNDI lookup, outbound network I/O, or filesystem access), regardless of the
type check that follows.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively
-via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which consults a
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed upstream in OpenNLP
+2.5.9 (and 3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; the fix consults a
package-prefix allowlist <em>before</em> calling <code>Class.forName()</code>.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">¶</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
@@ -1387,9 +1915,8 @@ exposed.</p>
<p>The most reliable mitigation is to <strong>not enable the OpenNLP-backed <code>analysis-extras</code> or <code>langid</code>
modules</strong> unless they are required. If you do use OpenNLP, load model files only from locations you
fully control and never from untrusted or user-supplied sources.</p>
-<p>In Solr 9.11.0 the upstream allowlist defense is backfilled at the application layer, since the
-vulnerable jar cannot yet be upgraded (Solr must track the OpenNLP version used by
-<code>lucene-analysis-opennlp</code>). Every OpenNLP model is loaded as a resource through Solr's resource
+<p>As defense in depth, Solr 9.11 also validates OpenNLP models at the application layer before they
+reach <code>ExtensionLoader</code>. Every OpenNLP model is loaded as a resource through Solr's resource
loaders, so the archive is validated at that single chokepoint before OpenNLP is allowed to
deserialize it:</p>
<ul>
@@ -1404,11 +1931,14 @@ deserialize it:</p>
</ul>
<p>Solr's own usage only ever references built-in <code>opennlp.*</code> factories, so legitimate models load
unchanged; only crafted models that try to instantiate arbitrary classes are blocked.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p>
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> is fixed — it upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the
+1.9.x backport) and adds the application-layer allowlist described above — and Solr <strong>10.1</strong> upgrades
+to 2.5.9. The affected (exploitable) range is therefore <strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 (plus Solr's
+own allowlist) closes this issue.</p>
<h4>References</h4>
<ul>
@@ -1423,7 +1953,7 @@ range is therefore 7.3.0 – 10.0.0.</p>
<strong>Status:</strong>
<span class="cdx-exploitable">exploitable</span>
</p>
- <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-10.0.0</p>
+ <p class="subheader"><strong>Affected Solr versions:</strong> 7.3.0-9.10.1,10.0.0</p>
</div>
</header>
@@ -1436,9 +1966,10 @@ who can supply a crafted dictionary file — either directly or embedded in a mo
OpenNLP deserializes — can therefore read local files from the server or trigger outbound requests
(server-side request forgery). Other OpenNLP XML parsing paths route through the hardened
<code>XmlUtil.createSaxParser()</code> helper, but this code path does not.</p>
-<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr pulls in transitively via
-<code>lucene-analysis-opennlp</code> (Lucene 9.12.3). There is a <code>opennlp-tools-1.9.5</code> release happening, but it hasn't finished or been integrated into Solr 9; the issue is fixed in OpenNLP 2.5.9 (and 3.0.0-M3), which parse dictionaries with secure
-XML processing that rejects DOCTYPE declarations and external entities.</p>
+<p>The vulnerable code is present in the <code>opennlp-tools-1.9.4.jar</code> that Solr's 9.x line pulls in
+transitively via <code>lucene-analysis-opennlp</code> (Lucene 9.12.3). The issue is fixed in OpenNLP 2.5.9 (and
+3.0.0-M3), and backported to the 1.9.x line as <code>opennlp-tools-1.9.5</code>; all of these parse dictionaries
+with secure XML processing that rejects DOCTYPE declarations and external entities.</p>
<h4 id="when-solr-is-exposed">When Solr is exposed<a class="headerlink" href="#when-solr-is-exposed" title="Permanent link">¶</a></h4>
<p>OpenNLP is not part of a default Solr installation, but it is exploitable once the OpenNLP-backed
modules are enabled. The vulnerable dictionary-parsing code path becomes reachable when:</p>
@@ -1461,11 +1992,14 @@ archive passes through a single chokepoint before OpenNLP is allowed to deserial
to both standalone (filesystem configset) and SolrCloud (ZooKeeper) deployments, and whether the
dictionary is loaded by the <code>langid</code> / <code>analysis-extras</code> update processors or by the
schema-configured OpenNLP analyzers.</p>
-<p>This flaw is present in every OpenNLP release before 2.5.9 (fixed in 2.5.9 / 3.0.0-M3, backported to
-1.9.5). Solr has bundled OpenNLP (transitively, via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0, so
-every release from 7.3.0 through 10.0.0 ships an affected version (1.8.3 through 2.5.6). The affected
-range is therefore 7.3.0 – 10.0.0.</p>
-<p>Fully resolved in Solr 10.1 by upgrading the bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) to 2.5.9.</p>
+<p>Solr has bundled OpenNLP (via <code>lucene-analysis-opennlp</code>) since Solr 7.3.0. Every release from 7.3.0
+through the 9.10.x line ships an affected <code>opennlp-tools</code> (1.8.3 through 1.9.4), and Solr 10.0.0 ships
+the affected 2.5.6. Solr <strong>9.11</strong> upgrades to the patched <code>opennlp-tools</code> 1.9.5 (the 1.9.x backport)
+and Solr <strong>10.1</strong> upgrades to 2.5.9, so both are fixed. The affected (exploitable) range is therefore
+<strong>7.3.0 – 9.10.1 and 10.0.0</strong>.</p>
+<p>Note: advisory databases record the fix only as OpenNLP 2.5.9, so a dependency scanner may still flag
+the backported <code>opennlp-tools</code> 1.9.5 that Solr 9.11 ships — a false positive, since 1.9.5 contains the
+backported fix.</p>
<h4>References</h4>
<ul>
@@ -1750,7 +2284,7 @@ vulnerability is not exploitable in Solr.</p>
</p>
<p class="subheader">
<strong>Status:</strong>
- <span class="cdx-in-triage">in_triage</span>
+ <span class="cdx-not-affected">not_affected</span>
</p>
<p class="subheader"><strong>Affected Solr versions:</strong> 4.4.0-9.9.0</p>
</div>
@@ -1758,6 +2292,20 @@ vulnerability is not exploitable in Solr.</p>
<h4>Description</h4>
<p>When parsing unknown fields in the Protobuf Java Lite and Full library, a maliciously crafted message can cause a StackOverflow error and lead to a program crash.</p>
+<p>Solr is <strong>not affected</strong>. The crafted-message DoS requires an attacker to feed protobuf input to a
+parser, and Solr exposes no such path:</p>
+<ul>
+<li><strong>Solr's own code never uses protobuf.</strong> There is no <code>com.google.protobuf</code> usage anywhere in the
+ Solr codebase, and Solr's client-facing APIs speak javabin, JSON and XML — never protobuf. The SQL
+ module is reached through <code>SQLHandler</code> (Calcite runs in-process, returning tuples); Solr exposes no
+ Avatica/protobuf wire endpoint to clients.</li>
+<li><strong>protobuf-java is only used to talk to trusted infrastructure.</strong> It is pulled in transitively for
+ communication with operator-controlled endpoints — the ZooKeeper ensemble, Hadoop RPC (HDFS /
+ Kerberos), the Google Cloud Storage backup API, the OpenTelemetry OTLP collector, and the Kafka
+ cross-DC pipeline. An external attacker cannot supply the deeply-nested message the DoS requires to
+ any of those parsers.</li>
+</ul>
+<p>Tracked upstream as SOLR-17833.</p>
<p>CVE-2024-7254 affects all <code>protobuf-java</code> releases before 3.25.5 (per the upstream advisory the
flaw was introduced at version 0, and is fixed in 3.25.5 / 4.27.5 / 4.28.2). Apache Solr has bundled
<code>protobuf-java</code> (transitively, via Hadoop and ZooKeeper) since <strong>Solr 4.4.0</strong> (which shipped 2.4.0a),