Quick answers
- Is CVE-2026-31960 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31960 being exploited in the wild.
- How severe is CVE-2026-31960?
- Medium severity, with a CVSS score of 5.3, published 11 March 2026.
- Which products and versions are affected?
- github.com/anchore/quill (Go) < 0.7.1, SEMVER:introduced=0,fixed=0.7.1.
- Is there a fix for CVE-2026-31960?
- Yes. github.com/anchore/quill (Go): upgrade to 0.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-31960 attacked?
- It is attacked from the adjacent network, in a software library.
- Am I affected by CVE-2026-31960?
- Check whether you run github.com/anchore/quill (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/anchore/quill (Go): upgrade to 0.7.1 or later
go get github.com/anchore/quill@v0.7.1
Technical details
Quill versions prior to v0.7.1 fail to impose a size limit when reading HTTP response bodies into memory during the Apple notarization process (CWE-770). An attacker capable of modifying API responses from Apple's notarization service—such as through a compromised certificate authority or a TLS-intercepting proxy—can deliver an arbitrarily large payload. This results in an out-of-memory (OOM) condition, causing the Quill CLI or library to crash. The vulnerability is primarily an availability risk and is mitigated by standard HTTPS/TLS validation unless the trust boundary is already compromised. The issue is fixed in version 0.7.1.
Affected products
- Anchore Quill < 0.7.1
Identifiers
- CVE-2026-31960
- GHSA-g32c-4pvp-769g
- GO-2026-4672
Timeline
- 2026-03-10: patched: Fixed in version v0.7.1
- 2026-03-11: advisory