Memory-exhaustion crash via unbounded index allocation
Published Aug 5, 2026 · Updated Aug 5, 2026
Excessive memory allocation in Apache Lucy allows context-dependent attackers to crash applications through a crafted search index. Freezer deserialization accepts a size value read by InStream from the index and allocates the declared amount without enforcing an upper bound. Exploitation requires an embedding application to open an attacker-controlled index, and memory exhaustion interrupts only that application or its service.
Summary
What happened
Excessive memory allocation in Apache Lucy allows context-dependent attackers to crash applications through a crafted search index. Freezer deserialization accepts a size value read by InStream from the index and allocates the declared amount without enforcing an upper bound. Exploitation requires an embedding application to open an attacker-controlled index, and memory exhaustion interrupts only that application or its service.
The record
- CVE
- CVE-2026-61485
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Lucy
- Classifications
- CWE-789, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo