Skip to main content
VulnerabilityPublished

CVE-2026-31961: anchore quill · Unthrottled Resource Allocation

Affects anchore quillSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.7.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.7.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade quill and anchore/quill to 0.7.1.

Affected software

ProductAffectedFixed in
anchorequillAffected
  • <0.7.1
Fixed in
  • 0.7.1
GitHubanchore/quillpkg:github/anchore/quillOther threatsAffected
  • <0.7.1
Fixed in
  • 0.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade Anchore Quill to version 0.7.1 or later, where this vulnerability is fixed. Until upgrading, implement strict validation and filtering of Mach-O binaries submitted for signing, rejecting files with suspiciously large or inconsistent size fields in the LC_CODE_SIGNATURE load command and embedded structures. Employ resource limits and monitoring on build and signing servers to detect and prevent excessive memory usage by Quill processes. Consider sandboxing or isolating the Quill process to limit the impact of crashes. In CI/CD pipelines, restrict who can submit binaries for signing and audit submissions for anomalies. Use runtime memory monitoring tools to alert on unusual memory allocation patterns during binary parsing. Additionally, review and harden the overall binary submission workflow to prevent untrusted or malformed binaries from reaching the signing stage. Maintain up-to-date vulnerability scanning and patch management practices to promptly address future issues.

Description

Quill provides simple mac binary signing and notarization from any platform. 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. This vulnerability is fixed in 0.7.1.

References

Community reviews

Loading reviews…