dbcve.org
QuillApplication · Anchore

CVE-2026-31959

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to after 0.7.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges 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 a Server-Side Request Forgery (SSRF) vulnerability when attempting to fetch the Apple notarization submission logs. Exploitation requires the ability to modify API responses from Apple's notarization service, which is not possible under standard network conditions due to HTTPS with proper TLS certificate validation; however, environments with TLS-intercepting proxies (common in corporate networks), compromised certificate authorities, or other trust boundary violations are at risk. When retrieving submission logs, Quill fetches a URL provided in the API response without validating that the scheme is https or that the host does not point to a local or multicast IP address. An attacker who can tamper with the response can supply an arbitrary URL, causing the Quill client to issue HTTP or HTTPS requests to attacker-controlled or internal network destinations. This could lead to exfiltration of sensitive data such as cloud provider credentials or internal service responses. Both the Quill CLI and library are affected when used to retrieve notarization submission logs. 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 before v0.7.1 contains an SSRF vulnerability where it fetches URLs from Apple notarization API responses without validating the scheme (should be https) or checking that the host doesn't resolve to local/multicast IP addresses. An attacker who can tamper with API responses (e.g., via TLS-intercepting proxy or compromised CA) can cause Quill to make requests to arbitrary internal or attacker-controlled destinations, potentially exfiltrating credentials or internal service data.

MitigationUpgrade Quill to version v0.7.1 or later which includes proper URL validation. If upgrade is not immediately possible, avoid using Quill in environments with TLS-intercepting proxies or untrusted certificate authorities.

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine installed Quill version
    Run `quill --version` or check the package/version metadata for your Quill installation
    Affected if The version displayed is 0.7.1 or lower (any version from 0.x up to and including 0.7.1)
  2. Check if Apple notarization feature is in use
    Review Quill configuration files or command arguments for settings related to Apple notarization, code signing, or iOS/macOS package validation
    Affected if Quill is configured to fetch or process Apple notarization API responses or validate Apple packages
  3. Identify TLS-intercepting proxies or untrusted CAs
    Inspect system proxy settings, corporate CA certificates installed on the host, or TLS inspection appliance configurations that could intercept Quill's outbound HTTPS traffic
    Affected if A TLS-intercepting proxy or untrusted certificate authority is present between Quill and Apple's notarization API endpoints

You are affected if Quill version 0.7.1 or lower is installed AND the Apple notarization feature is enabled AND your environment permits TLS interception (through a proxy or compromised CA), allowing an attacker to inject malicious URLs into API responses.

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 a release after 0.7.1
Interim mitigation

Upgrade Quill to version v0.7.1 or later which includes proper URL validation. If upgrade is not immediately possible, avoid using Quill in environments with TLS-intercepting proxies or untrusted certificate authorities.

Recommended fix High confidence

v0.7.1

  1. Download or install Quill version v0.7.1 or later from the official GitHub releases repository (github.com)
  2. Ensure any CI/CD pipelines or build systems that use Quill are updated to reference v0.7.1 or newer
  3. After upgrading, verify that notarization workflows continue to function correctly with the new version

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

Fix this in Quill Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31959 — 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-31959 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