Fastllm
Monthly
A heap/stack buffer overflow in fastllm (versions up to and including 0.1.8.2) lets remote attackers corrupt memory by supplying a crafted GGUF model file whose string-length field is manipulated, triggering an out-of-bounds write inside GGUFBuffer::ReadString in third_party/gguf/gguf.cpp. Exploitation requires the victim to load or parse the malicious model (user interaction, CVSS UI:P/UI:R), and no authentication is needed; impact is limited to partial confidentiality, integrity, and availability loss. Publicly available exploit code exists (a POC archive is linked alongside the VulDB entry and upstream GitHub issue 759), but there is no CISA KEV listing, so active in-the-wild exploitation is not confirmed; the vendor has not yet responded to the report.
Heap/stack buffer overflow in ztxz16 fastllm through 1.8.2, triggered inside SafeTensorItem::CreateBuffer (src/model.cpp) when a crafted safetensors file supplies manipulated data_offsets values during model weight loading. An attacker who convinces an operator to load an untrusted model file can cause out-of-bounds memory writes, yielding limited confidentiality, integrity, and availability impact; publicly available exploit code exists (VulDB submission with a poc.zip attachment) but there is no evidence of active exploitation in the wild. The vendor has not responded to the upstream issue report, so no fix has been published, and exploitation requires user interaction - the victim must explicitly load the malicious weights - which keeps this a moderate, low-priority supply-chain/untrusted-model-file issue rather than a remotely reachable server compromise.
A heap/stack buffer overflow in fastllm (versions up to and including 0.1.8.2) lets remote attackers corrupt memory by supplying a crafted GGUF model file whose string-length field is manipulated, triggering an out-of-bounds write inside GGUFBuffer::ReadString in third_party/gguf/gguf.cpp. Exploitation requires the victim to load or parse the malicious model (user interaction, CVSS UI:P/UI:R), and no authentication is needed; impact is limited to partial confidentiality, integrity, and availability loss. Publicly available exploit code exists (a POC archive is linked alongside the VulDB entry and upstream GitHub issue 759), but there is no CISA KEV listing, so active in-the-wild exploitation is not confirmed; the vendor has not yet responded to the report.
Heap/stack buffer overflow in ztxz16 fastllm through 1.8.2, triggered inside SafeTensorItem::CreateBuffer (src/model.cpp) when a crafted safetensors file supplies manipulated data_offsets values during model weight loading. An attacker who convinces an operator to load an untrusted model file can cause out-of-bounds memory writes, yielding limited confidentiality, integrity, and availability impact; publicly available exploit code exists (VulDB submission with a poc.zip attachment) but there is no evidence of active exploitation in the wild. The vendor has not responded to the upstream issue report, so no fix has been published, and exploitation requires user interaction - the victim must explicitly load the malicious weights - which keeps this a moderate, low-priority supply-chain/untrusted-model-file issue rather than a remotely reachable server compromise.