Application crash via invalid external-variable pointers
Published Sep 22, 2026 · Updated Sep 22, 2026
Memory corruption in YARA 4.5.8 allows attackers to crash applications by supplying a crafted compiled .yrc rule file. During deserialization, insufficient validation leaves external-variable pointers able to reach yr_rules_destroy() as invalid allocations or yr_object_create() as wild references. Exploitation requires an application to load the attacker-supplied compiled rules; the documented consequence is memory corruption followed by an application crash.
Summary
What happened
Memory corruption in YARA 4.5.8 allows attackers to crash applications by supplying a crafted compiled .yrc rule file. During deserialization, insufficient validation leaves external-variable pointers able to reach yr_rules_destroy() as invalid allocations or yr_object_create() as wild references. Exploitation requires an application to load the attacker-supplied compiled rules; the documented consequence is memory corruption followed by an application crash.
The record
- CVE
- CVE-2026-88340
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started