Skip to main content
CybersecurityHQ Structural Conditions Board
Primary navigation
Issue 46 · as of Issue No. 46, 12 November 2026 (observation cutoff 9 November 2026; collection closed 9 November, 16:28 UTC) · Snapshot ea7de8184295

Correction: an integrity check reported a digest that is not the delivered file's, without saying so

Every record in this file was ratified by the publisher on 2026-11-12 and is in force. The declared field gives the date the correction was first recorded.

id
CHQ-CORR-2026-024
class
CORRECTION
subtype
provenance
status
IN FORCE
authority
DM ratified 2026-11-12
effective
2026-11-12
published
2026-11-12
title
Correction: an integrity check reported a digest that is not the delivered file's, without saying so
what was wrong
On 1 November 2026 the integrity gate's store check recorded one digest for the registry artifact while the delivered file hashed to another. The check passed and did not say that the digest it recorded described the file before the gate wrote its own results into it.
what is true
Both digests are correct for what they describe. The first is the artifact as the gate read it; the second is the delivered file, and it is the one named in the separate attestation, which also records that the store was rebuilt from those exact bytes. A file cannot carry its own hash, so the value recorded inside the artifact can never equal the delivered digest.
what changed
The check's detail now states that its digest is the pre-write digest and names the attestation that carries the delivered one. The artifact is no longer sent for review without its attestation.
what did not change
No digest, count, rating or Outlook.
control analysis
The control worked and its report was ambiguous. Two reviewers hashed the file independently, which is the right check, and could not complete it because the attestation did not travel with the artifact.
found by
An external adversarial review.