Advisory record · GHSA-mjvf-4h88-6xm3

Improper Authentication vulnerability in Apache Solr

CVSS 9.8 CriticalCriticalEPSS 0.93 · 99th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.93 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 16 Oct 2024, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.solr:solrMaven>=5.3.0, <8.11.4 || >=9.0.0, <9.7.08.11.4, 9.7.0
Identifiers
GHSA-mjvf-4h88-6xm3 · BIT-solr-2024-45216 · CVE-2024-45216
Weakness (CWE)
CWE-287 · CWE-863
Published
16 Oct 2024
Updated
2 Jul 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Solr versions from 5.3.0 before 8.11.4 and from 9.0.0 before 9.7.0 are vulnerable to an authentication bypass when the PKIAuthenticationPlugin is in use, which is enabled by default when Solr Authentication is configured. An unauthenticated attacker with network access to the Solr API can append a crafted suffix to an API URL path so that requests skip authentication while still reaching the original endpoint. Upgrade to Solr 8.11.4 or 9.7.0.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.93, the 99th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.