Local compiler crash via recursive type signatures
Published Feb 21, 2026 · Updated Feb 21, 2026
Uncontrolled recursion in aardappel Lobster 2025.0 through 2025.4 allows local users to crash the compiler with a crafted source file. The TypeName, Signature, and FormatArg routines repeatedly expand a self-referential function type without a recursion-depth guard. Executing the file locally exhausts the process stack and terminates the compiler; no confidentiality or integrity impact is reported.
Summary
What happened
Uncontrolled recursion in aardappel Lobster 2025.0 through 2025.4 allows local users to crash the compiler with a crafted source file. The TypeName, Signature, and FormatArg routines repeatedly expand a self-referential function type without a recursion-depth guard. Executing the file locally exhausts the process stack and terminates the compiler; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2026-2887
- Published
- Feb 21, 2026
- Updated
- Feb 21, 2026
- Vendor
- aardappel
- Product
- Lobster
- Classifications
- CWE-674, CWE-404, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 21, 2026CVE publishedPublication date reported by the CVE source.
- Feb 21, 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=2025.0
- Affected versionversion=2025.1
- Affected versionversion=2025.2
- Affected versionversion=2025.3
- Affected versionversion=2025.4
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
- repro.lobster compiler stack-overflow proof of conceptproof of concept · demonstrated
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