MONAI check_hash returned a successful result when the expected digest argument was None, despite documentation presenting the operation as an integrity check. The weak state arises when a model or dataset retrieval call lacks a pinned hash and an adversary can modify the downloaded bytes. A substituted model artifact could pass a nominal hash-checking…
Inspect the ClaimsCase · DiggingBeagle record
MONAI model download verification reported success with no expected hash
MONAI check_hash returned a successful result when the expected digest argument was None, despite documentation presenting the operation as an integrity check. A substituted model artifact could pass a nominal hash-checking step without actually being authenticated against known content.
The weak state arises when a model or dataset retrieval call lacks a pinned hash and an adversary can modify the downloaded bytes. The advisory does not establish an exploited hospital download, and the possible chain to executable bundle logging has not been observed.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- AI role
- AGAINST AI
Basis and provenance
The cited primary technical report or advisory supports the stated mechanism within its reported scope. The assessment does not infer a production breach, a victim count or a comparable impact score from a laboratory result. No verified deployed fix and effectiveness can be established from the reviewed material. Boundary: An integrity-check function returning success with no expected digest is not proof that the downloaded artifact matches a trusted publisher.
Assessed Oct 29, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP23-MONAI-MISSING-HASH-1 · CLM-ENRICH-20261029-17 · MONAI missing expected download hash accepted advisory
At a glance
A substituted model artifact could pass a nominal hash-checking step without actually being authenticated against known content.
Read the implicationsThe advisory does not establish an exploited hospital download, and the possible chain to executable bundle logging has not been observed.
Limits and uncertaintyFull account
MONAI check_hash returned a successful result when the expected digest argument was None, despite documentation presenting the operation as an integrity check.
The weak state arises when a model or dataset retrieval call lacks a pinned hash and an adversary can modify the downloaded bytes. A substituted model artifact could pass a nominal hash-checking step without actually being authenticated against known content.
The advisory does not establish an exploited hospital download, and the possible chain to executable bundle logging has not been observed. Require an actual trusted expected digest or signed manifest for every artifact and reject verification calls without a usable trust anchor.
Evidence interpretation and control boundary. An integrity-check function returning success with no expected digest is not proof that the downloaded artifact matches a trusted publisher. A caller would need a controlled download or substituted artifact for this to become an attack, and the separately reported executable logging configuration creates a possible compound path, not an observed exploit chain. A real verifier must fail closed on absent hashes or validate an independent signed manifest.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Claims & evidence
CLM-ENRICH-20261029-17The MONAI security advisory reports check_hash accepting a missing expected hash value as success, allowing download paths without an externally pinned digest to appear verified.supported
Basis: reported finding
- supportsMONAI missing expected download hash accepted advisoryprimary disclosure
GHSA-hhh4-h52m-fqh6: check_hash(hash_val=None), downloader call sites, remediation caveats
CLM-CP23-MONAI-MISSING-HASH-1MONAI check_hash returned a successful result when the expected digest argument was None, despite documentation presenting the operation as an integrity check. The weak state arises when a model or dataset retrieval call lacks a pinned hash and an adversary can modify the downloaded bytes. A substituted model artifact could pass a nominal hash-checking step without actually being authenticated against known content.supported
Basis: reported finding
- supportsMONAI missing expected download hash accepted advisoryprimary disclosure
GHSA-hhh4-h52m-fqh6: check_hash(hash_val=None), downloader call sites, remediation caveats
Implications
A substituted model artifact could pass a nominal hash-checking step without actually being authenticated against known content.
Controls and mitigations
- Require an actual trusted expected digest or signed manifest for every artifact and reject verification calls without a usable trust anchor.
Unknowns and contradictions
- The advisory does not establish an exploited hospital download, and the possible chain to executable bundle logging has not been observed.
Sources and citation
Material revision history
- Oct 29, 2026 · Canonical change recorded · new in release · revision 202