CVE-2026-22022Disclosure(apache / solr)

LOWCVSS 8.2 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch apache solr systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Deployments of Apache Solr 5.3.0 through 9.10.0 that rely on Solr's "Rule Based Authorization Plugin" are vulnerable to allowing unauthorized access to certain Solr APIs, due to insufficiently strict input validation in those components.  Only deployments that meet all of the following criteria are impacted by this vulnerability: * Use of Solr's "RuleBasedAuthorizationPlugin" * A RuleBasedAuthorizationPlugin config (see security.json) that specifies multiple "roles" * A RuleBasedAuthorizationPlugin permission list (see security.json) that uses one or more of the following pre-defined permission rules: "config-read", "config-edit", "schema-read", "metrics-read", or "security-read". * A RuleBasedAuthorizationPlugin permission list that doesn't define the "all" pre-defined permission * A networking setup that allows clients to make unfiltered network requests to Solr. (i.e. user-submitted HTTP/HTTPS requests reach Solr as-is, unmodified or restricted by any intervening proxy or gateway) Users can mitigate this vulnerability by ensuring that their RuleBasedAuthorizationPlugin configuration specifies the "all" pre-defined permission and associates the permission with an "admin" or other privileged role.  Users can also upgrade to a Solr version outside of the impacted range, such as the recently released Solr 9.10.1.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-285

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • solr

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
solr

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-04-02: 1Patch / Workaround · 2026-04-02: 1Technical Details · 2026-04-02: 104-02
Signal classification1 categories
Disclosure
1100.0%
Full discourse1 post
  • HeroDevs@herodevs
    Disclosure

    🚨 Two new CVEs in Apache Solr — and they’re hitting where teams least expect it. CVE-2026-22022 and CVE-2026-22444 expose gaps in authorization and file access controls — putting sensitive configuration data, file systems, and even credentials at risk. Why this matters: ✔️ No authentication required for certain exploit paths ✔️ Sensitive data exposure through misconfigured APIs ✔️ Widely used versions affected across enterprise environments Moving from Solr 8 to 9+ can mean Java upgrades, API changes, and months of migration work... HeroDevs Never-Ending Support (NES) for Apache Solr & Lucene delivers patched, drop-in replacements for EOL versions — so you can remediate now and migrate on your timeline. Because security issues don’t wait for your roadmap. #ApacheSolr #Java #CVE #AppSec #OpenSourceSecurity #EOL #DevSecOps #HeroDevs

    Post summary

    The post announces two new Apache Solr CVEs that expose authorization gaps and allow sensitive data exposure, while highlighting available patched replacements for immediate remediation.

    10001112
    2.7K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appapachesolr---

Explore more