`CVE-2026-44825` Apache solr

Affected software	Apache solr
Severity	9.8 Critical CVSS 3.1 2 scores
Weakness	Hard-coded credentials (CWE-798)
Published	1 Jun 2026
Updated	2 Nov 2026

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

CWE-1188

Exploitation status

Exploited

Real-world exploitation reported by VulnCheck KEV. CISA has not confirmed it.

CISA KEV not listed
VulnCheck KEV listed Exploitation reported in the wild. 1 citation · honeypot sightings · 3 exploits · earliest 2026-07-22.
CISA Vulnrichment exploitation: none
Indexed PoC 3 indexed Published artifacts you can open, in GitHub PoC, Nuclei; first seen 2026-07-03.
EPSS 3.9% chance in 30 days

VulnCheck KEV

Exploitation evidence from VulnCheck Known Exploited Vulnerabilities (VulnCheck KEV), used under VulnCheck's community terms. View CVE-2026-44825 in VulnCheck (free account).

Evidence	Source	Detail	Date
Honeypot sighting	VulnCheck canaries	Exploitation attempts seen on 1 day	2026-10-21
Reported exploitation	research.empiricalsecurity.com	/research/july-2026-cve-of-the-month	2026-07-22
Exploit reference	VulnCheck XDB 510c61328b83	Exploit type: remote-with-credentials	2026-07-08
Exploit reference	VulnCheck XDB d50c12b9169a	Exploit type: initial-access	2026-10-14
Exploit reference	VulnCheck XDB e0726b7c8d19	Exploit type: remote-with-credentials	2026-10-15

Evidence

Source

Detail

Date

Honeypot sighting

VulnCheck canaries

Exploitation attempts seen on 1 day

2026-10-21

Reported exploitation

research.empiricalsecurity.com

/research/july-2026-cve-of-the-month

2026-07-22

Exploit reference

VulnCheck XDB 510c61328b83

Exploit type: remote-with-credentials

2026-07-08

Exploit reference

VulnCheck XDB d50c12b9169a

Exploit type: initial-access

2026-10-14

Exploit reference

VulnCheck XDB e0726b7c8d19

Exploit type: remote-with-credentials

2026-10-15

Index	Artifact	Stars	First seen
GitHub PoC	Apache Solr instances that may be affected by CVE-2026-44825, related to Velocity Template Remote Code Execution (RCE) conditions.	12	2026-07-08
GitHub PoC	☄️ Mass reconnaissance & exploitation framework for Apache Solr CVE-2026-44825 — Velocity template injection to RCE	5	2026-07-03
Nuclei	Apache Solr 9.4.0-9.10.1 / 10.0.0 - Hardcoded Default Credentials

Waratek protection

Outside Waratek scope

A Java vulnerability, but not one Waratek protects. It affects only Java on a user's desktop (applets, Web Start, JavaFX, the installer), sits in a product the Waratek agent can't be installed into, or is in a package we don't expect in business applications. The decision below says which.

Protection none
Action not pursued none
Review human Researcher
Record active

Decided by	A researcher's recorded decision for this specific CVE
Finding	A researcher set this CVE's status to Outside Waratek scope.

Decided by

A researcher's recorded decision for this specific CVE

Finding

A researcher set this CVE's status to Outside Waratek scope.

Waratek research note

written 2026-11-13

Written by a Waratek engineer who reviewed this CVE. Their decision sets the status above, ahead of every automated rule except a withdrawal.

Comments

No ARMR patch is needed: this is a configuration problem with an easy manual workaround.

bin/solr auth enable in Apache Solr 9.4.0–9.10.1 and 10.0.0 silently adds template users (superadmin, admin, search, index) with publicly known default passwords to security.json, alongside the account the administrator asked for. Anyone who knows those defaults can log in as a full administrator. The flaw is in the credentials the setup tool writes, not in code that handles a malicious request at runtime. A login with valid (if well-known) credentials is legitimate traffic as far as the JVM can tell, so there is nothing for an ARMR rule to hook.

Workaround: delete the template users from security.json, or give them strong passwords. Clusters that did not use bin/solr auth enable to bootstrap BasicAuth are not affected. The permanent fix is to upgrade to Solr 9.11.0 or 10.1.0.

CVSS

9.8 CRITICAL v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 9.8 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H NVD Primary published

CVSS 3.1 8.1 HIGH CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H security@apache.org Secondary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	9.8	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`	NVD	Primary	published
CVSS 3.1	8.1	HIGH	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`	security@apache.org	Secondary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.apache.solr:solr-core 9.4.0 none 9.10.1

org.apache.solr:solr-core unspecified none unbounded

Package	Introduced	Fixed	Last affected
`org.apache.solr:solr-core`	9.4.0	none	9.10.1
`org.apache.solr:solr-core`	unspecified	none	unbounded

Products and versions

2 products, 4 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	apache	solr	generic	≥ 9.4.0 and ≤ 9.10.1 · 10.0.0
osv	org.apache.solr	solr-core	generic	any version · ≥ 9.4.0 and ≤ 9.10.1

Source

Vendor

Product

Scheme

Affected versions

nvd

apache

solr

generic

≥ 9.4.0 and ≤ 9.10.1 · 10.0.0

osv

org.apache.solr

solr-core

generic

any version · ≥ 9.4.0 and ≤ 9.10.1

References

URL	Tags
https://github.com/apache/lucene-solr	PACKAGE
https://lists.apache.org/thread/5xg6xr99glocp3zsg9ht2zlbwlrst7ch	WEB
http://www.openwall.com/lists/oss-security/2026/05/29/6	WEB

URL

Timeline

Published	2026-06-01	By the CVE Program.
NVD record modified	2026-07-22	NVD's own last-modified date for this record.
VulnCheck KEV: earliest evidence	2026-07-22	Date of the oldest evidence of exploitation in VulnCheck KEV's record. VulnCheck does not publish the date it listed the CVE.
VulnCheck KEV: latest evidence	2026-10-21	Date of the newest report, exploit reference or honeypot sighting in VulnCheck KEV's record.
Last VRT activity	2026-11-02	Most recent commit touching this CVE's classification, patch or rule file.
Classification created	2026-11-13	First commit adding this CVE's research note.

Published

2026-06-01

By the CVE Program.

NVD record modified

2026-07-22

NVD's own last-modified date for this record.

VulnCheck KEV: earliest evidence

2026-07-22

Date of the oldest evidence of exploitation in VulnCheck KEV's record. VulnCheck does not publish the date it listed the CVE.

VulnCheck KEV: latest evidence

2026-10-21

Date of the newest report, exploit reference or honeypot sighting in VulnCheck KEV's record.

Last VRT activity

2026-11-02

Most recent commit touching this CVE's classification, patch or rule file.

Classification created

2026-11-13

First commit adding this CVE's research note.

How VRT decided (4 of 24 rules ran)

4 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification decided it matched Outside Waratek scope A researcher set this CVE's status to Outside Waratek scope.

5 manual classification not reached Manual classification of this CVE in the legacy dataset

6 non-java-upstream not reached A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component not reached The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side not reached Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven not reached An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint not reached A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven not reached The affected package being open source on Maven, so the fix can be read

19 poc-derivable not reached An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit not reached Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match not reached A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc not reached Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold not reached Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published not reached Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

NVD ↗ · CVE.org ↗