Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.3
Quill Crashes When Notarizing with Large Apple Response
GHSA-g32c-4pvp-769g
CVE-2026-31960
Summary
Quill, a tool for notarizing macOS software, can crash if it receives a large response from Apple's notarization service through a compromised corporate network or proxy. This only affects Quill's ability to function, not the security of the software being notarized. Update to Quill version 0.7.1 to fix this issue.
What to do
- Update github.com anchore to version 0.7.1.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| github.com | anchore | <= 0.7.1 | 0.7.1 |
Original title
Quill has DoS via unbounded read of HTTP response body during notarization
Original description
### Impact
Quill before version `v0.7.1` has unbounded reads of HTTP response bodies during the Apple notarization process. 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 processing HTTP responses during notarization, Quill reads the entire response body into memory without any size limit. An attacker who can control or modify the response content can return an arbitrarily large payload, causing the Quill client to run out of memory and crash. The impact is limited to availability; there is no effect on confidentiality or integrity. Both the Quill CLI and library are affected when used to perform notarization operations.
### Patches
Fixed in Quill version `v0.7.1`
### Workarounds
None
### Credit
Anchore would like to thank opera-aklajn (Opera) for reporting this vulnerability
### Resources
- [Apple Get Submission Log API Documentation](https://developer.apple.com/documentation/notaryapi/get-submission-log)
Quill before version `v0.7.1` has unbounded reads of HTTP response bodies during the Apple notarization process. 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 processing HTTP responses during notarization, Quill reads the entire response body into memory without any size limit. An attacker who can control or modify the response content can return an arbitrarily large payload, causing the Quill client to run out of memory and crash. The impact is limited to availability; there is no effect on confidentiality or integrity. Both the Quill CLI and library are affected when used to perform notarization operations.
### Patches
Fixed in Quill version `v0.7.1`
### Workarounds
None
### Credit
Anchore would like to thank opera-aklajn (Opera) for reporting this vulnerability
### Resources
- [Apple Get Submission Log API Documentation](https://developer.apple.com/documentation/notaryapi/get-submission-log)
ghsa CVSS3.1
5.3
Vulnerability type
CWE-770
Allocation of Resources Without Limits
- https://github.com/anchore/quill/security/advisories/GHSA-g32c-4pvp-769g
- https://github.com/anchore/quill/commit/9cdb0823ea1d2c45dcc11557f8c5cd7291c75d29
- https://developer.apple.com/documentation/notaryapi/get-submission-log
- https://github.com/anchore/quill/releases/tag/v0.7.1
- https://github.com/advisories/GHSA-g32c-4pvp-769g
- https://nvd.nist.gov/vuln/detail/CVE-2026-31960
Published: 11 Mar 2026 · Updated: 14 Mar 2026 · First seen: 11 Mar 2026