Denial of service from memory exhaustion in github.com/notaryproject/notation-go (CVE-2023-25656) | HOL Guard CVE

High · CVSS 7.5CVE-2023-25656GHSA-87X9-7GRX-M28V

Denial of service from memory exhaustion in github.com/notaryproject/notation-go

Answer in brief

CVE-2023-25656 records a High severity (CVSS 7.5) vulnerability in Denial of service from memory exhaustion in github.com/notaryproject/notation-go. The current sources do not mark it as known exploited. The current feed maps github.com/notaryproject/notation-go (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Feb 22, 2023Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Aug 7, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/notaryproject/notation-go (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/notaryproject/notation-gogo	>=0 <1.0.0-rc.3	1.0.0-rc.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/notaryproject/notation-go.
Review the reported fix. Update github.com/notaryproject/notation-go to 1.0.0-rc.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Feb 22, 2023
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

### Impact `notation-go` users will find their application using excessive memory when verifying signatures and the application will be finally killed, and thus availability is impacted. ### Patches The problem has been patched in the release [v1.0.0-rc.3](https://github.com/notaryproject/notation-go/releases/tag/v1.0.0-rc.3). Users should upgrade their `notation-go` packages to `v1.0.0-rc.3` or above. ### Workarounds Users can review their own trust policy file and check if the identity string contains `=#`. Meanwhile, users should only put trusted certificates in their trust stores referenced by their own trust policy files, and make sure the `authenticity` validation is set to `enforce` ### Credits The `notation-go` project would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing this issue during a security fuzzing audit sponsored by CNCF and Shiwei Zhang (@shizhMSFT) for root cause analysis and detailed vulnerability report. ### References - [Resource exhaustion attacks](https://en.wikipedia.org/wiki/Resource_exhaustion_attack)

Quoted source text, attributed separately from HOL analysis.