Skip to main content
Public proof of conceptFix available

CVE-2026-44825

A public proof of concept exists; no exploitation attested.

  • Published2026-06-01
  • WeaknessCWE-1188 · CWE-798

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC
  1. 2026-06-0109:16CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-44825?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-44825?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Apache solr
BranchAffectedFixed in
9.x≥ 9.4.0, ≤ 9.10.1no fix published
10.0= 10.0.0no fix published
solr
BranchAffectedFixed in
10.0≥ 9.4.0, < 10.0.010.0.0
10.0≥ 10.0.0, ≤ 10.0.0no fix published
solr-core
BranchAffectedFixed in
9.x≥ 9.4.0, ≤ 9.10.1no fix published
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

read 2026-10-23 19:25 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
3 repositories, unverifiedshinthink/solrradargagaltotal/CVE-2026-44825-Apache-Solr-Scannerq0524/CVE-2026-44825_CTF
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2026-06-01
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.18.1read 2026-10-23
  • NVDCVSS 3.19.8read 2026-10-23
  • CNAweakness (CWE)CWE-1188, CWE-798read 2026-10-23
  • FIRST EPSSEPSS score2.8 %2026-10-23
  • PoC-in-GitHubproof of concept3read 2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-06-01
Last Modified
2026-07-22
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-44825?

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

Is CVE-2026-44825 actively exploited?

Active exploitation of CVE-2026-44825 has not been confirmed. Its EPSS score was 2.8% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-44825?

CVE-2026-44825 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running solr? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month