dbcve.org
SolrApplication · Apache

CVE-2026-44825

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-01
Fix available
A fix is available. Upgrade to after 9.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Solr's Basic Authentication setup tool (bin/solr auth enable) installs hardcoded default template users (superadmin, admin, search, index) alongside any user-specified account. These publicly known default credentials provide remote attackers with full administrative cluster access.

MitigationImmediately delete the template users from security.json or change their passwords to strong values. Until fixed versions are available, verify no default credentials remain active.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:>= 9.4.0, <= 9.10.1= 10.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Solr version
    Run `bin/solr -version` or inspect the version string in the output of `bin/solr status`
    Affected if The version is 9.4.0 through 9.10.1 inclusive, or exactly 10.0.0
  2. Verify if Basic Authentication is enabled
    Run `bin/solr auth status` or check for the presence of security.json in the server/solr directory
    Affected if Basic Authentication has been enabled using `bin/solr auth enable`
  3. Inspect security.json for template users
    Examine the contents of the security.json file (typically in server/solr/security.json or the ZooKeeper config if using SolrCloud) and look for user entries named superadmin, admin, search, or index
    Affected if Any of these four template users (superadmin, admin, search, index) exist in the authentication credentials section of security.json
  4. Confirm credentials were not changed
    Review security.json to verify whether the template user passwords have been changed from their default values (the default passwords are publicly known and match the usernames: superadmin:superadmin, admin:admin, search:search, index:index)
    Affected if The template users exist with their default password values or with passwords that have not been changed from the known defaults

A user is affected if they run Solr 9.4.0-9.10.1 or 10.0.0, enabled Basic Authentication using bin/solr auth enable, and have not removed or changed the passwords of the template users (superadmin, admin, search, index) from their default values in security.json.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.10.1
Interim mitigation

Immediately delete the template users from security.json or change their passwords to strong values. Until fixed versions are available, verify no default credentials remain active.

Recommended fix High confidence

9.11.0 for Solr 9.x branches; 10.1.0 for Solr 10.x branch

  1. 1. Identify your current Solr version by running `bin/solr version` or checking the solr-*-release.jar filename
  2. 2. Backup your current security.json file (typically found in $SOLR_HOME/server/solr/security/security.json or in ZooKeeper if using SolrCloud)
  3. 3. If running Solr 9.x (9.4.0 through 9.10.1), upgrade to version 9.11.0
  4. 4. If running Solr 10.0.0, upgrade to version 10.1.0
  5. 5. After upgrade, verify that the template users (superadmin, admin, search, index) have been removed from security.json
  6. 6. If the hardcoded users still exist in security.json, manually remove them or change their passwords to strong unique values
  7. 7. Restart Solr to apply changes
  8. 8. Verify that authentication works correctly with your intended admin credentials
Caveat Review Solr release notes for 9.11.0 and 10.1.0 for any potential breaking changes between versions; test upgrade in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solr Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44825 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data