Halibut Project maintains a documentation-generation tool with a focused product footprint centered on the Halibut application itself. The recurring vulnerability signal centers on memory-safety issues, specifically use-after-free and double-free conditions typical of native-code implementations. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Halibut Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-42614HIGH A use after free in info_width_internal in bk_info.c in Halibut 1.2 allows an attacker to cause a segmentation fault or possibly have unspecified other impact via a crafted text do | May 24, 2022 | 7.8 | 26 | NO | NO |
CVE-2021-42613HIGH A double free in cleanup_index in index.c in Halibut 1.2 allows an attacker to cause a denial of service or possibly have other unspecified impact via a crafted text document. | May 24, 2022 | 7.8 | 26 | NO | NO |
CVE-2021-42612HIGH A use after free in cleanup_index in index.c in Halibut 1.2 allows an attacker to cause a segmentation fault or possibly have other unspecified impact via a crafted text document. | May 24, 2022 | 7.8 | 25 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Halibut Project.
Media articles that mention a CVE ID that affects a product developed by Halibut Project — matched by CVE ID, not by vendor name.