gerlowskija commented on code in PR #261:
URL: https://github.com/apache/solr-site/pull/261#discussion_r4630385618
##########
content/solr/solr_news/2026-11-19-java4shell-cve-2026-114938.md:
##########
@@ -0,0 +1,53 @@
+Title: Apache Solr and Java4Shell (CVE-2026-114938)
+category: solr/news
+save_as:
+
+*From the Apache Solr PMC*
+
+A critical OpenJDK RCE vulnerability, CVE-2026-114938 ("Java4Shell"), was
disclosed on November 17, 2026. It is a vulnerability in the Java runtime
(OpenJDK), **not in Apache Solr** - but Solr was publicly named as an
application where exploitation was demonstrated, so users should act.
+
+**The fix is to update your JDK.** No Solr release addresses this, because the
bug is not in Solr.
+
+### Does it affect my Solr?
+
+Your deployment is affected only if **ALL three** conditions are met:
+
+1. The JDK is OpenJDK 17.0.6 or later (Temurin, Corretto, Zulu, Red Hat,
Oracle, etc.).
+2. The CPU is x86-64 with AVX-512 VBMI (Intel Ice Lake / Sapphire Rapids /
Emerald Rapids / Granite Rapids; AMD Zen 4+). ARM/Apple Silicon is not
affected. To check on Linux: `grep -o 'avx512vbmi' /proc/cpuinfo`
+3. A reachable path decodes attacker-controlled Base64.
Review Comment:
[0] This is a hard thing for users to really understand and act on. Even as
someone involved in the project for many years who has focused a lot of time on
our APIs in particular, **I** don't feel like I could fully enumerate the APIs
or plugins that this would cover.
Can we come up with at least a partial list to help folks?
[0] Is it worth clarifying what "reachable" means here? I assume we mean
both that the path is reachable via the network and that the "path" is
something pre-auth or that an untrusted-but-authenticated user has access to?
##########
content/solr/solr_news/2026-11-19-java4shell-cve-2026-114938.md:
##########
@@ -0,0 +1,53 @@
+Title: Apache Solr and Java4Shell (CVE-2026-114938)
+category: solr/news
+save_as:
+
+*From the Apache Solr PMC*
+
+A critical OpenJDK RCE vulnerability, CVE-2026-114938 ("Java4Shell"), was
disclosed on November 17, 2026. It is a vulnerability in the Java runtime
(OpenJDK), **not in Apache Solr** - but Solr was publicly named as an
application where exploitation was demonstrated, so users should act.
+
+**The fix is to update your JDK.** No Solr release addresses this, because the
bug is not in Solr.
+
+### Does it affect my Solr?
+
+Your deployment is affected only if **ALL three** conditions are met:
+
+1. The JDK is OpenJDK 17.0.6 or later (Temurin, Corretto, Zulu, Red Hat,
Oracle, etc.).
+2. The CPU is x86-64 with AVX-512 VBMI (Intel Ice Lake / Sapphire Rapids /
Emerald Rapids / Granite Rapids; AMD Zen 4+). ARM/Apple Silicon is not
affected. To check on Linux: `grep -o 'avx512vbmi' /proc/cpuinfo`
+3. A reachable path decodes attacker-controlled Base64.
+
+### What to do
+
+1. **Update your JDK** to a patched build (Oracle Nov 2026 CPU / OpenJDK
2026-11-17 advisory). Patched builds end in `.1`:
+ * Java 17 → 17.0.21.1
+ * Java 21 → 21.0.13.1
+ * Java 25 → 25.0.5.1
+ * Java 27 → 27.0.1.1
+2. **Restart every Solr node** after patching — a running JVM stays vulnerable
until restarted.
+3. **If you can't patch yet**, start the JVM with `-XX:-UseBASE64Intrinsics`
or `-XX:UseAVX=2` (x86-64 only). Do **not** use
`-XX:DisableIntrinsic=_base64_decodeBlock` alone — it can break JVM startup.
+
+### Official Solr container images
+
+If you run Solr using our [official container
images](https://hub.docker.com/_/solr):
+
+* Make sure you're on a [supported tag](https://hub.docker.com/_/solr). If
you're not, upgrade.
+* Supported images are rebuilt regularly with the latest JRE and Linux patches
and published under the same tags.
+* **Patched images are not available yet.** The Solr images are built on
Eclipse Temurin, and a rebuilt Solr image can only be published once patched
Temurin base images are released. That may take anywhere from hours to days.
+* **Don't wait for the new image. Apply the JVM flag now.** Set
`SOLR_OPTS="-XX:-UseBASE64Intrinsics"` on your current containers (e.g. `docker
run -e SOLR_OPTS="-XX:-UseBASE64Intrinsics" …`) and recreate them. This
protects you on the image you're already running.
+* **Once the patched image is published**, re-pull it and recreate your
containers. This won't happen on its own for images you're already running. If
you pin by digest (`solr@sha256:…`), switch to the new digest once you've
confirmed it has the patched Java. After that you can remove the JVM flag.
+* To check which Java version you have, look at the JVM section of the Solr
Admin UI dashboard, or run `docker run --rm solr:<tag> java -version`. It
should show one of the patched versions listed above (e.g. 17.0.21.1,
21.0.13.1) or later.
+
+### Why authentication matters
+
+RCE against Solr was demonstrated as a **post-authentication** issue — an
attacker must get past Solr's auth first. That protects you only if auth is
actually enabled. **Solr does not require authentication by default**, and
deployments that rely on network isolation alone get no benefit from the
"post-auth" qualifier: anyone who can reach the endpoint can reach the
vulnerable path.
Review Comment:
[0] I'm behind on some of the discussion, but are BasicAuth users vulnerable
even with authentication? If so, we should make sure to mention that here so
that folks don't see "post-authentication issue" and think they're great.
(If BasicAuth's use of base64 decoding isn't subject to this, then ignore
this comment.)
##########
content/solr/solr_news/2026-11-19-java4shell-cve-2026-114938.md:
##########
@@ -0,0 +1,53 @@
+Title: Apache Solr and Java4Shell (CVE-2026-114938)
+category: solr/news
+save_as:
+
+*From the Apache Solr PMC*
+
+A critical OpenJDK RCE vulnerability, CVE-2026-114938 ("Java4Shell"), was
disclosed on November 17, 2026. It is a vulnerability in the Java runtime
(OpenJDK), **not in Apache Solr** - but Solr was publicly named as an
application where exploitation was demonstrated, so users should act.
+
+**The fix is to update your JDK.** No Solr release addresses this, because the
bug is not in Solr.
+
+### Does it affect my Solr?
+
+Your deployment is affected only if **ALL three** conditions are met:
+
+1. The JDK is OpenJDK 17.0.6 or later (Temurin, Corretto, Zulu, Red Hat,
Oracle, etc.).
+2. The CPU is x86-64 with AVX-512 VBMI (Intel Ice Lake / Sapphire Rapids /
Emerald Rapids / Granite Rapids; AMD Zen 4+). ARM/Apple Silicon is not
affected. To check on Linux: `grep -o 'avx512vbmi' /proc/cpuinfo`
+3. A reachable path decodes attacker-controlled Base64.
+
+### What to do
+
+1. **Update your JDK** to a patched build (Oracle Nov 2026 CPU / OpenJDK
2026-11-17 advisory). Patched builds end in `.1`:
+ * Java 17 → 17.0.21.1
+ * Java 21 → 21.0.13.1
+ * Java 25 → 25.0.5.1
+ * Java 27 → 27.0.1.1
+2. **Restart every Solr node** after patching — a running JVM stays vulnerable
until restarted.
+3. **If you can't patch yet**, start the JVM with `-XX:-UseBASE64Intrinsics`
or `-XX:UseAVX=2` (x86-64 only). Do **not** use
`-XX:DisableIntrinsic=_base64_decodeBlock` alone — it can break JVM startup.
+
+### Official Solr container images
+
+If you run Solr using our [official container
images](https://hub.docker.com/_/solr):
+
+* Make sure you're on a [supported tag](https://hub.docker.com/_/solr). If
you're not, upgrade.
+* Supported images are rebuilt regularly with the latest JRE and Linux patches
and published under the same tags.
Review Comment:
```suggestion
** Supported images are rebuilt regularly with the latest JRE and Linux
patches and published under the same tags.
```
This makes more sense as a sub-bullet IMO, since it's clarifying what the
significance of "Supported" is in the bullet above.
##########
content/solr/solr_news/2026-11-19-java4shell-cve-2026-114938.md:
##########
@@ -0,0 +1,53 @@
+Title: Apache Solr and Java4Shell (CVE-2026-114938)
+category: solr/news
+save_as:
+
+*From the Apache Solr PMC*
+
+A critical OpenJDK RCE vulnerability, CVE-2026-114938 ("Java4Shell"), was
disclosed on November 17, 2026. It is a vulnerability in the Java runtime
(OpenJDK), **not in Apache Solr** - but Solr was publicly named as an
application where exploitation was demonstrated, so users should act.
+
+**The fix is to update your JDK.** No Solr release addresses this, because the
bug is not in Solr.
+
+### Does it affect my Solr?
+
+Your deployment is affected only if **ALL three** conditions are met:
+
+1. The JDK is OpenJDK 17.0.6 or later (Temurin, Corretto, Zulu, Red Hat,
Oracle, etc.).
+2. The CPU is x86-64 with AVX-512 VBMI (Intel Ice Lake / Sapphire Rapids /
Emerald Rapids / Granite Rapids; AMD Zen 4+). ARM/Apple Silicon is not
affected. To check on Linux: `grep -o 'avx512vbmi' /proc/cpuinfo`
+3. A reachable path decodes attacker-controlled Base64.
+
+### What to do
+
+1. **Update your JDK** to a patched build (Oracle Nov 2026 CPU / OpenJDK
2026-11-17 advisory). Patched builds end in `.1`:
+ * Java 17 → 17.0.21.1
+ * Java 21 → 21.0.13.1
+ * Java 25 → 25.0.5.1
+ * Java 27 → 27.0.1.1
+2. **Restart every Solr node** after patching — a running JVM stays vulnerable
until restarted.
+3. **If you can't patch yet**, start the JVM with `-XX:-UseBASE64Intrinsics`
or `-XX:UseAVX=2` (x86-64 only). Do **not** use
`-XX:DisableIntrinsic=_base64_decodeBlock` alone — it can break JVM startup.
+
+### Official Solr container images
+
+If you run Solr using our [official container
images](https://hub.docker.com/_/solr):
+
+* Make sure you're on a [supported tag](https://hub.docker.com/_/solr). If
you're not, upgrade.
+* Supported images are rebuilt regularly with the latest JRE and Linux patches
and published under the same tags.
+* **Patched images are not available yet.** The Solr images are built on
Eclipse Temurin, and a rebuilt Solr image can only be published once patched
Temurin base images are released. That may take anywhere from hours to days.
Review Comment:
[0] If the patched images aren't available **now** then it doesn't make all
that much sense to lead with that entry. Instead lets lead with the sysprop
workaround. That keeps our instructions in the order that is actually
follow-able by users.
##########
content/solr/solr_news/2026-11-19-java4shell-cve-2026-114938.md:
##########
@@ -0,0 +1,53 @@
+Title: Apache Solr and Java4Shell (CVE-2026-114938)
+category: solr/news
+save_as:
+
+*From the Apache Solr PMC*
+
+A critical OpenJDK RCE vulnerability, CVE-2026-114938 ("Java4Shell"), was
disclosed on November 17, 2026. It is a vulnerability in the Java runtime
(OpenJDK), **not in Apache Solr** - but Solr was publicly named as an
application where exploitation was demonstrated, so users should act.
+
+**The fix is to update your JDK.** No Solr release addresses this, because the
bug is not in Solr.
+
+### Does it affect my Solr?
+
+Your deployment is affected only if **ALL three** conditions are met:
+
+1. The JDK is OpenJDK 17.0.6 or later (Temurin, Corretto, Zulu, Red Hat,
Oracle, etc.).
+2. The CPU is x86-64 with AVX-512 VBMI (Intel Ice Lake / Sapphire Rapids /
Emerald Rapids / Granite Rapids; AMD Zen 4+). ARM/Apple Silicon is not
affected. To check on Linux: `grep -o 'avx512vbmi' /proc/cpuinfo`
+3. A reachable path decodes attacker-controlled Base64.
+
+### What to do
+
+1. **Update your JDK** to a patched build (Oracle Nov 2026 CPU / OpenJDK
2026-11-17 advisory). Patched builds end in `.1`:
+ * Java 17 → 17.0.21.1
+ * Java 21 → 21.0.13.1
+ * Java 25 → 25.0.5.1
+ * Java 27 → 27.0.1.1
+2. **Restart every Solr node** after patching — a running JVM stays vulnerable
until restarted.
+3. **If you can't patch yet**, start the JVM with `-XX:-UseBASE64Intrinsics`
or `-XX:UseAVX=2` (x86-64 only). Do **not** use
`-XX:DisableIntrinsic=_base64_decodeBlock` alone — it can break JVM startup.
+
+### Official Solr container images
+
+If you run Solr using our [official container
images](https://hub.docker.com/_/solr):
+
+* Make sure you're on a [supported tag](https://hub.docker.com/_/solr). If
you're not, upgrade.
+* Supported images are rebuilt regularly with the latest JRE and Linux patches
and published under the same tags.
+* **Patched images are not available yet.** The Solr images are built on
Eclipse Temurin, and a rebuilt Solr image can only be published once patched
Temurin base images are released. That may take anywhere from hours to days.
+* **Don't wait for the new image. Apply the JVM flag now.** Set
`SOLR_OPTS="-XX:-UseBASE64Intrinsics"` on your current containers (e.g. `docker
run -e SOLR_OPTS="-XX:-UseBASE64Intrinsics" …`) and recreate them. This
protects you on the image you're already running.
Review Comment:
Is this system property something that we should mention for users outside
of the Docker context as well? Or is it truly only applicable here?
It's hard to envision a concrete scenario but I can imagine folks for whom
it's easier to update a system property than install a new JDK version across
their entire fleet.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]