Quick answers
- Is CVE-2026-31959 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31959 being exploited in the wild.
- How severe is CVE-2026-31959?
- 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-31959?
- 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-31959 attacked?
- It is attacked from the adjacent network, in a software library.
- Am I affected by CVE-2026-31959?
- 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 are vulnerable to Server-Side Request Forgery (SSRF) during the retrieval of Apple notarization submission logs. The application fetches a URL provided in the Apple Notary API response without validating the protocol scheme (e.g., ensuring it is HTTPS) or verifying that the destination host is not a local or multicast IP address. Exploitation requires the ability to modify API responses, which typically necessitates a TLS-intercepting proxy, a compromised Certificate Authority, or a man-in-the-middle position within a trusted boundary. An attacker successfully manipulating the response can force the Quill client to issue requests to arbitrary internal or external destinations, potentially exfiltrating sensitive metadata or service responses. The issue is fixed in version 0.7.1.
Affected products
- anchore quill < 0.7.1
Identifiers
- CVE-2026-31959
- GHSA-7q3q-5px6-4c5p
- GO-2026-4671
Timeline
- 2026-03-10: patched: Fixed in version v0.7.1
- 2026-03-11: disclosed: GitHub Advisory published