malformed proposed intoto entries can cause a panic (CVE-2023-33199) | HOL Guard CVE

Medium · CVSS 5.3CVE-2023-33199GHSA-FRQX-JFCM-6JJR

malformed proposed intoto entries can cause a panic

Answer in brief

CVE-2023-33199 records a Medium severity (CVSS 5.3) vulnerability in malformed proposed intoto entries can cause a panic. The current sources do not mark it as known exploited. The current feed maps github.com/sigstore/rekor (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 May 26, 2023Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 5.3. 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/sigstore/rekor (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/sigstore/rekorgo	>=0 <1.2.0	1.2.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/sigstore/rekor.
Review the reported fix. Update github.com/sigstore/rekor to 1.2.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
May 26, 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
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Impact A malformed proposed entry of the `intoto/v0.0.2` type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal. ### Patches This is fixed in v1.2.0 of Rekor. ### Workarounds No ### References Discovered by OSS-Fuzz

Quoted source text, attributed separately from HOL analysis.