CVE-2024-45216 — solr
CRITICALCVE-2024-45216 is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in org.apache.solr:solr. EPSS puts its 30-day exploitation probability at 92.7% (100th percentile). A fix is available for org.apache.solr:solr — see the affected versions and patch details below.
Apache Solr: Authentication bypass possible using a fake URL Path ending
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45216.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2024-45216 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.solr:solr☕org.apache.solr:solrReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Improper Authentication vulnerability in Apache Solr.
Solr instances using the PKIAuthenticationPlugin, which is enabled by default when Solr Authentication is used, are vulnerable to Authentication bypass. A fake ending at the end of any Solr API URL path, will allow requests to skip Authentication while maintaining the API contract with the original URL Path. This fake ending looks like an unprotected API path, however it is stripped off internally after authentication but before API routing.
This issue affects Apache Solr: from 5.3.0 before 8.11.4, from 9.0.0 before 9.7.0.
Users are recommended to upgrade to version 9.7.0, or 8.11.4, which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.solr:solr | ≥ 5.3.0&&< 8.11.4 | 8.11.4org.apache.solr:solr:8.11.4 |
| ☕Maven | org.apache.solr:solr | ≥ 9.0.0&&< 9.7.0 | 9.7.0org.apache.solr:solr:9.7.0 |
Affected Products
solrapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.solr:solr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.solr:solr to 8.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45216 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
How to detect CVE-2024-45216
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-45216 -u https://target- Template
- Apache Solr - Authentication Bypass
- Severity
- critical
- Impact
- Users are recommended to upgrade to version 9.7.0, or 8.11.4, which fix the issue.
- Remediation
- Apply the latest security patches and updates from the vendor to address this vulnerability.
Template by ProjectDiscovery nuclei-templates (gumgum), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-45216 in your dependencies?
Find it across Maven, including transitive dependencies.