Skip to main content
VulnerabilityPublished

CVE-2026-104895: Solr · asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken

Affects solrSource GCVE Database

0
Compare
Authoritative record:CVE-2026-104895· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 10.0.0-r12 soon.

Data as of 11 Nov 2026, 04:17 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (HeroDevs)CVSS 3.17.5
Patch
Available – fixed in 10.0.0-r12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade solr to 10.0.0-r12.

Affected software

ProductAffectedFixed in
CleanStartsolrpkg:apk/cleanstart/solrOther threatsAffected
  • <10.0.0-r12
Fixed in
  • 10.0.0-r12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Solr to version 10.0.0-r12 or later, where this vulnerability is fixed. Since a patch is available, applying the official fix is the recommended mitigation.

Description

A high-severity vulnerability in Apache Solr's asynchronous Smile parser (NonBlockingByteArrayParser) allows untrusted input to specify a raw-binary length prefix used to allocate a byte array without upper bound or overflow checks. This can lead to denial of service by exhausting system resources. The issue affects Solr versions prior to 10.0.0-r12 and has been fixed in 10.0.0-r12.

References

Community reviews

Loading reviews…