On this page

Atomicorp WAF Research Note: CVE-2026-44825

Apache Solr 9.4.0-9.10.1 / 10.0.0 - Hardcoded Default Credentials

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-44825
  • Name: Apache Solr 9.4.0-9.10.1 / 10.0.0 - Hardcoded Default Credentials
  • Severity: Critical
  • CVSS: 9.8 (v3.1) (Critical)
  • CVSS version: 3.1
  • CVSS source: NVD
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: High
  • CWE: CWE-798 — Use of Hard-coded Credentials, CWE-1188 — Initialization of a Resource with an Insecure Default
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-191 , CAPEC-665 , CAPEC-70
  • Vendor: apache
  • Vulnerable product: solr
  • CVE published: 2026-06-01
  • CVE last modified: 2026-07-22
  • Affected versions (NVD configurations):
    • solr: >= 9.4.0, <= 9.10.1
    • solr: 10.0.0
  • EPSS: 0.0289; 86.1th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 330925
  • Matching rules: 1; rules with blocking actions: 1
  • Would-block Rule IDs: 330925
  • Request surfaces inspected: Request headers
Technical CPE data

This section lists vulnerable CPE matches retained from the NVD configurations. It supplements the readable affected-product information above.

  • cpe:2.3:a:apache:solr:*:*:*:*:*:*:*:*
    • Version start (inclusive): 9.4.0
    • Version end (inclusive): 9.10.1
    • NVD match criteria ID: A3AD8B90-4676-4179-B497-6DA0F4CA6D57
  • cpe:2.3:a:apache:solr:10.0.0:*:*:*:*:*:*:*
    • NVD match criteria ID: 3DFFDA22-2A21-432B-96C2-97D430B2D79F

Vulnerability 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

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (330925 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: Apache Software Foundation Apache Solr versions through 9.10.1.
    • Affected versions: Apache Software Foundation Apache Solr version 10.0.0.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .