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

CVE-2026-44825 + Apache Solr has hardcoded credentials in the Basic Authentication setup tool + High + 2026-06-01

One-sentence business risk

Broken authentication or authorization can expose tenant data and administrator actions, which buyers treat as a release blocker.

Research notes

  • Root cause: 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 instal.
  • Affected versions: maven:org.apache.solr:solr-core >= 9.4.0, <= 9.10.1; maven:org.apache.solr:solr-core = 10.0.0.
  • Fixed / safe versions: Vendor-fixed release.
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: use upstream advisory score .

Exact vulnerable code pattern

curl --netrc "https://user@example.com/"  # URL username can select an unintended .netrc password

Fixed / mitigated code pattern

omit URL usernames when using .netrc, pin the host+login pair explicitly, and upgrade curl/libcurl to the fixed release

Dependency or runtime update:

mvn -q dependency:tree | grep -i solr-core || true
# update Maven/Gradle coordinates to Vendor-fixed release

Step-by-step integration guide

  1. Inventory org.apache.solr:solr-core across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to Vendor-fixed release or apply the exact vendor patch referenced below.
  3. Replace the vulnerable credential-leak pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-44825-apache-solr-has-hardcoded-credentials-in-the-bas
source: "GitHub Advisory Database"
dependency_or_product: "org.apache.solr:solr-core"
affected: "maven:org.apache.solr:solr-core >= 9.4.0, <= 9.10.1; maven:org.apache.solr:solr-core = 10.0.0"
fixed: "Vendor-fixed release"
signals:
  - "credential-leak"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-44825 (Apache Solr has hardcoded credentials in the Basic Authentication setup tool) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to Vendor-fixed release. Replace the vulnerable credential-leak pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-44825, credential-leak, org.apache.solr:solr-core, GitHub Advisory Database.
  • Affected tech stack: java/maven.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References