CVE-2026-44825 — solr-core
HIGHCVE-2026-44825 is a high-severity (CVSS 8.1) Hard-coded Credentials vulnerability in org.apache.solr:solr-core. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Apache Solr: Enabling BasicAuth using bin/solr CLI configures additional insecure users
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-44825.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.solr:solr-core☕org.apache.solr:solr-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.solr:solr-core | ≥ 9.4.0 | No fix |
| ☕Maven | org.apache.solr:solr-core | all versions | No fix |
Affected Products
solrapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.solr:solr-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.solr:solr-core for CVE-2026-44825. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
How to detect CVE-2026-44825
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2026-44825 -u https://target- Template
- Apache Solr 9.4.0-9.10.1 / 10.0.0 - Hardcoded Default Credentials
- Severity
- high
- Impact
- Remote attackers can gain full administrative access to the cluster using default credentials.
- Remediation
- Upgrade to versions 9.11.0, 10.1.0 or later; alternatively, delete template users or change their passwords in security.json.
Template by ProjectDiscovery nuclei-templates (pdteam, 0x_Akoko), MIT licensed. View the full template. Scan only systems you are authorised to test.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This flaw is rated as Important because it allows a remote attacker to gain full administrative access to an Apache Solr cluster. When the `bin/solr auth enable` tool is used to set up Basic Authentication, publicly known default credentials are silently installed alongside user-specified accounts. This can lead to…
To mitigate this issue, administrators must either delete the default template users (superadmin, admin, search, index) from `security.json` or promptly change their passwords after employing the `bin/solr auth enable` tool. This action prevents unauthorized administrative access to the Solr cluster. A restart or reload of the Solr service may be necessary for these changes to be applied effectively.Source: Red Hat security advisory for CVE-2026-44825 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-44825 in your dependencies?
Find it across Maven, including transitive dependencies.