Skip to content

CVE-2026-44825

Use of Hard-coded Credentials: Is CVE-2026-44825 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Yes
VulnCheck KEV · Jul 22, 2026
Public exploit
PoC (unverified)
Metasploit/EDB/PoC
Base severity
8.1 High
CVSS
Exploitation prob.
0.5%
FIRST EPSS
Weakness
CWE-798 · Use of Hard-coded Credentials
CWE

Reported exploited in the wild (VulnCheck KEV), though not in CISA KEV yet. Treat it as urgent and check your exposure.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
None
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track
  • high impact → Track*

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

public exploits

links to sources — we don’t host code

Unverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.

affected packages

GHSA-qhr7-h655-pw6r · GitHub rates it high
  • Mavenorg.apache.solr:solr-core
    Vulnerable
    ≥ 9.4.0, ≤ 9.10.1
    Fixed in
    no patched version listed

Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.

baseline read

auto · not a community verdict

Real, but low real-world risk

A genuine vulnerability on paper, but EPSS shows little real-world exploitation — the base score may overstate urgency. This is not the same as a false positive.

Based on CVSS · FIRST EPSS

Confirm or dispute →
Affected:Apache

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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

Published

Embed this verdict
TruePositive verdict for CVE-2026-44825
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-44825/badge.svg)](https://www.truepositive.app/cve/CVE-2026-44825)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-44825"><img src="https://www.truepositive.app/cve/CVE-2026-44825/badge.svg" alt="TruePositive verdict for CVE-2026-44825"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. Added to VulnCheck KEV · reported exploited in the wild
  2. CISA SSVC assessment · exploitation: none
  3. Published by NVD

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    This scores high on paper (CVSS 8.1) but the real-world signal is low. It is not in CISA KEV and no public exploit was found, and near-term exploitation looks unlikely (EPSS about 1%). Verify your own exposure before treating it as urgent. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile. Not an emergency for most teams, but patch it in your normal cycle and check whether the affected component is actually exposed in your setup.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-798 · Use of Hard-coded Credentials.