Vulnerability in solr (CVE-2026-44825)
Summary
Vulnerability in solr (CVE-2026-44825). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 10.0.0 or later.
Original description
The description as published by the source.
Hardcoded credentials in the Basic Authentication setup tool (bin/solr auth enable) in Apache Solr versions 9.4.0 through 9.10.1 and 10.0.0 allows a remote attacker to gain full administrative access to the cluster via publicly known default credentials installed silently alongside the user-specified account.
As an immediate workaround without upgrading, delete the template users (superadmin, admin, search, index) from security.json or change their passwords.
The future, not yet released, versions 9.11.0 and 10.1.0 will not be vulnerable, and it will be enough to upgrade to solve the issue.
Not affected:
- Clusters where bin/solr auth enable was not used to bootstrap BasicAuth
- Clusters where template users have been assigned strong passwords after bootstrap
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44825 has been found in solr.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade solr to 10.0.0 or later.
If unsure, ask your IT team or search "solr CVE-2026-44825" on the vendor's site.
CVE-2026-44825 (solr) — CWE-798 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 10.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-798) exists in solr.
Check the vendor advisory for the affected versions of solr.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 10.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'solr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'solr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
solrを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade solr to 10.0.0ステージング環境で 10.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-44825 lucene-solr
References
- advisory lists.apache.org
- advisory openwall.com
- package github.com
- web nvd.nist.gov
- web github.com