Skip to content

Cap CVE-2025-48734 (commons-beanutils) range at 9.10.1/10.0.0 — fixed in 9.11/10.1 #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
epugh merged 1 commit into from
Aug 13, 2026
+8 −2
Merged

Cap CVE-2025-48734 (commons-beanutils) range at 9.10.1/10.0.0 — fixed in 9.11/10.1 #229

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions content/solr/vex/2026-07-18-cve-2025-48734.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
cve: CVE-2025-48734
category:
- solr/vex
versions: "3.6.0-10.0.0"
versions: "3.6.0-9.10.1, 10.0.0"
jars:
- commons-beanutils-1.9.4.jar
analysis:
Expand All @@ -15,4 +15,10 @@ CVE-2025-48734 allows an attacker to access the JVM ClassLoader (and potentially
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
therefore 3.6.0 – 10.0.0.
therefore 3.6.0 – 9.10.1 plus 10.0.0.

The fix has landed on all active development branches: Solr 9.11 (`branch_9x`), 10.1 (`branch_10x`),
and `main` upgrade the bundled copy to commons-beanutils 1.11.0, and Hadoop 3.4.3 (shipped in 9.11)
additionally dropped the shaded commons-beanutils it previously carried inside `hadoop-client-runtime`.
So 9.11 and 10.1 are not affected, and the range is capped at 9.10.1 / 10.0.0 rather than an open
`3.6.0 – 10.0.0` that would otherwise sweep in the fixed 9.11 release.