Is CVE-2026-44825 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44825 being exploited in the wild.

How severe is CVE-2026-44825?

High severity, with a CVSS score of 8.1, published 1 June 2026.

Which products and versions are affected?

org.apache.solr:solr-core (Maven) ECOSYSTEM:introduced=9.4.0,last_affected=9.10.1.

Is there a fix for CVE-2026-44825?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-44825 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-44825?

Check whether you run org.apache.solr:solr-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44825: Apache Solr hardcoded credentials in Basic Authentication setup tool

CVE-2026-44825 · Severity: high · CVSS 8.1 · Published 2026-06-01

Apache Solr is a popular open-source search platform used to index and search large volumes of data. A security flaw in its authentication setup tool creates hidden, administrative accounts with well-known default passwords when a user enables basic security. An attacker can use these secret accounts to gain full control over the search cluster, potentially leading to the theft or modification of sensitive indexed data.

Technologies: org.apache.solr:solr-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-44825 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44825 being exploited in the wild.
How severe is CVE-2026-44825?: High severity, with a CVSS score of 8.1, published 1 June 2026.
Which products and versions are affected?: org.apache.solr:solr-core (Maven) ECOSYSTEM:introduced=9.4.0,last_affected=9.10.1.
Is there a fix for CVE-2026-44825?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-44825 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-44825?: Check whether you run org.apache.solr:solr-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Use of Hard-coded Credentials (CWE-798) vulnerability exists in the Apache Solr 'bin/solr auth enable' CLI tool. When this tool is used to bootstrap Basic Authentication, it silently installs several template accounts (superadmin, admin, search, index) with publicly known default credentials alongside the user-defined account. A remote attacker can exploit these credentials to gain full administrative access to the Solr cluster. The vulnerability affects versions 9.4.0 through 9.10.1 and 10.0.0. Users are advised to manually delete these template users from security.json or change their passwords until patches 9.11.0 or 10.1.0 are released.

Affected products

Apache Solr 9.4.0 through 9.10.1, 10.0.0

Identifiers

CVE-2026-44825
GHSA-qhr7-h655-pw6r

Timeline

2026-05-29: disclosed: Initial disclosure on oss-security mailing list
2026-06-01: advisory: GitHub and NVD advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.