Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The notation-go Go module is vulnerable in versions before 1.0.0-rc.3. When verifying signatures, it can use excessive memory, which can cause the application to be killed and impact availability. The advisory does not specify what input triggers this or what level of access an attacker needs. Upgrade to notation-go 1.0.0-rc.3 or later. As a workaround, check whether your trust policy identity strings contain "=#", and make sure only trusted certificates are in trust stores and that authenticity validation is set to enforce.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0044, the 38th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:43 UTC First seen by agentprime
- 31 Oct 2026, 14:43 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-87x9-7grx-m28v
- OSV: GHSA-87x9-7grx-m28v
- github.com/notaryproject/notation-go/security/advisories/GHSA-87x9-7grx-m28v
- nvd.nist.gov/vuln/detail/CVE-2023-25656
- github.com/notaryproject/notation-go/pull/275
- github.com/notaryproject/notation-go
- github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3