Skip to content

CVE-2026-44825

Published: September 24, 2026

Choreo Labs products impacted: No

Customer action required: No


REPORTED VULNERABILITY

Hardcoded credentials in Apache Solr's Basic Authentication setup tool (bin/solr auth enable) allow a remote attacker to gain full administrative access to a Solr cluster via publicly known default credentials installed silently alongside the user-specified account, in Solr versions 9.4.0 through 9.10.1 and 10.0.0 1.

REPORTED PRODUCTS

  • WSO2 API Manager : 4.6.0

WSO2 JUSTIFICATION

solr-core is included transitively through the Apache Solr bundle, which supports Governance Registry content indexing in the product. The CVE-2026-44825 1 vulnerability is exploitable only when both of the following preconditions are met:

  1. The Solr cluster's Basic Authentication has been bootstrapped via the bin/solr auth enable command-line setup tool.
  2. The cluster's Solr HTTP API is reachable over the network by an attacker.

A thorough analysis of all Solr-related code paths in WSO2 API Manager confirms that neither precondition is met:

  • Precondition 1 – bin/solr auth enable is never invoked: While the AuthTool/SolrCLI classes that implement bin/solr auth enable are present in the bundled solr-core jar, WSO2 API Manager never invokes this command-line setup path. No template users or their default credentials are ever provisioned by the product.
  • Precondition 2 – No network-reachable Solr HTTP API: WSO2 API Manager does not run Solr as a standalone server process; it embeds Solr in-process via the EmbeddedSolrServer API (confirmed in the product's own startup log: "Default Embedded Solr Server Initialized"), so communication with Solr happens through direct in-process Java method calls rather than over HTTP. A full listing of the running product's listening TCP ports confirms that no Solr HTTP endpoint is exposed.

This matches the CVE record's own stated non-affected condition: "Not affected: Clusters where bin/solr auth enable was not used to bootstrap BasicAuth" 1.

Since neither precondition can be met, this vulnerability is not exploitable in WSO2 API Manager. In addition, as of the date of this justification, there is no fixed Solr release available among the 9.x versions included in WSO2 API Manager.

REFERENCES