dbcve.org
QuillApplication · Anchore

CVE-2026-31961

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 0.7.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Quill v0.7.1之前版本在解析Mach-O二进制文件时存在无限制内存分配漏洞。攻击者可在LC_CODE_SIGNATURE load command和SuperBlob/Blob结构中设置超大的DataSize、Count、Length等字段值，导致程序尝试分配远超文件大小的内存，造成内存耗尽和拒绝服务。

Mitigation将Quill升级到v0.7.1或更高版本以获得修复；在CI/CD等处理外部提交二进制文件的场景中，应增加内存限制或资源配额以缓解潜在攻击。

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
QuillApplication
Affected:< 0.7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Quill version
    Run `quill --version` or check the package manager output (e.g., `pip show anchore-quill`, `brew list quill --version`)
    Affected if Version is below 0.7.1 (e.g., 0.7.0, 0.6.x, etc.)
  2. Verify Mach-O file processing capability
    Check if Quill has processed or can process macOS/iOS binary files (.app, .dylib, .macho, binary executables) - review recent analysis logs, CI/CD job outputs, or analyze any input configuration that points to Mach-O files
    Affected if Quill is configured to parse or has recently parsed Mach-O format binaries (files with Mach-O headers)
  3. Confirm LC_CODE_SIGNATURE load command parsing is possible
    Review analysis output or logs for references to code signature parsing, or inspect a sample Mach-O binary with `otool -l <binary>` to verify LC_CODE_SIGNATURE load command exists in target files
    Affected if Target Mach-O binaries contain LC_CODE_SIGNATURE load commands that Quill will parse
  4. Check memory constraints on Quill execution
    Inspect system limits (`ulimit -a`), container/cgroup memory limits, or CI/CD resource configurations for the environment running Quill
    Affected if No memory limits are enforced or limits are set very high (unrestricted memory allocation is possible)

You are affected if you have Quill version below 0.7.1 and process Mach-O binary files that contain LC_CODE_SIGNATURE load commands, with no memory limits configured to restrict allocation attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.7.1 or later
Fixed in 0.7.1
Interim mitigation

将Quill升级到v0.7.1或更高版本以获得修复；在CI/CD等处理外部提交二进制文件的场景中，应增加内存限制或资源配额以缓解潜在攻击。

Recommended fix High confidence

v0.7.1

  1. Upgrade Quill to version v0.7.1 by obtaining the release from the Quill repository and rebuilding/installing the binary, or run 'go install github.com/nowsecurity/[email protected]' if using Go modules

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Quill Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31961 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data