{
  "claim_outcome": "confirmed",
  "claim_block_reason": null,
  "repro_result": "bypass_confirmed",
  "validated_surface": "library_api",
  "evidence_scope": "realistic_harness",
  "variant_kind": "fix_bypass",
  "claimed_impact_class": "other",
  "observed_impact_class": "other",
  "exploitability_confidence": "high",
  "attacker_controlled_input": "tlogEntries[].integratedTime + inclusionPromise.signedEntryTimestamp in a SignedEntity whose timestamp-providing tlog entry is absent from tlogEntries (decoupled), supplied to the public Verifier.verify(SignedEntity) API",
  "trigger_path": "Verifier.verify -> verifyTimestamps -> getTLogTimestamp (packages/verify/src/timestamp/index.ts) passes the fix's !entry.inclusionPromise presence-check because a FORGED inclusionPromise is present, returning the attacker-chosen integratedTime as a trusted timestamp; verifySigningKey/verifyCertificate (packages/verify/src/key/index.ts) accepts an EXPIRED certificate at that time; verifyTLogs (packages/verify/src/verifier.ts) is a no-op because tlogEntries is empty, so verifyTLogSET (packages/verify/src/tlog/set.ts) never validates the forged SET",
  "end_to_end_target_reached": true,
  "sanitizer_used": false,
  "crash_observed": false,
  "read_write_primitive_observed": false,
  "exploit_chain_demonstrated": true,
  "blocking_mitigation": null,
  "fix_assumption_bypassed": "The fix assumes inclusionPromise *presence* implies integratedTime is cryptographically bound (via verifyTLogSET in verifyTLogs). This only holds when the timestamp-providing tlog entry is also present in tlogEntries (as toSignedEntity couples them). A decoupled SignedEntity evades verifyTLogSET, so a forged inclusionPromise satisfies the presence-check while integratedTime remains unauthenticated.",
  "inferred": false,
  "tested_commits": {
    "vulnerable": "7845532f9d17f6f765363dbee82b01bd159fb52b",
    "fixed": "f074710a91ea9260a9ac2142345634579843a3cd"
  }
}