CVE-2026-31961: Quill has unbounded memory allocation via unvalidated size fields in Mach-O binary parsing
Quill before version v0.7.1 contains an unbounded memory allocation vulnerability when parsing Mach-O binaries. Exploitation requires that Quill processes an attacker-supplied Mach-O binary, which is most likely in environments such as CI/CD pipelines, shared signing services, or any workflow where externally-submitted binaries are accepted for signing.
When parsing a Mach-O binary, Quill reads several size and count fields from the LC_CODE_SIGNATURE load command and embedded code signing structures (SuperBlob, BlobIndex) and uses them to allocate memory buffers without validating that the values are reasonable or consistent with the actual file size. Affected fields include DataSize, DataOffset, and Size from the load command, Count from the SuperBlob header, and Length from individual blob headers. An attacker can craft a minimal (~4KB) malicious Mach-O binary with extremely large values in these fields, causing Quill to attempt to allocate excessive memory. This leads to memory exhaustion and denial of service, potentially crashing the host process. Both the Quill CLI and Go library are affected when used to parse untrusted Mach-O files.
References
- developer.apple.com/documentation/technotes/tn3126-inside-code-signing-hashes
- github.com/advisories/GHSA-xj69-m9qq-8m94
- github.com/anchore/quill
- github.com/anchore/quill/commit/80cf3fe082678af0ec4f9f8dd93f39189d2dc1fe
- github.com/anchore/quill/releases/tag/v0.7.1
- github.com/anchore/quill/security/advisories/GHSA-xj69-m9qq-8m94
- nvd.nist.gov/vuln/detail/CVE-2026-31961
Code Behaviors & Features
Detect and mitigate CVE-2026-31961 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →