{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-pin-issuer-keys-before-aaif-cross-issuer-trust-chain-verification-becomes-a-confused-deputy-vulnerability",
  "title": "Where must an instance pin issuer keys before AAIF cross-issuer trust chain verification becomes a confused-deputy vulnerability",
  "date_of_record": "2026 November 17",
  "scope": "Applies to AAIF (Agent Identity Attestation Framework) verifiers that accept delegation chains spanning more than one issuer (e.g., an orchestrator-issued root attestation delegating to a sub-agent whose own attestation is issued by a different AAIF authority). Does not apply to single-issuer, single-hop attestation verification, nor to chains where the verifier is also the sole issuer of every link.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-pin-issuer-keys-before-aaif-cross-issuer-trust-chain-verification-becomes-a-confused-deputy-vulnerability.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-pin-issuer-keys-before-aaif-cross-issuer-trust-chain-verification-becomes-a-confused-deputy-vulnerability.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-pin-issuer-keys-before-aaif-cross-issuer-trust-chain-verification-becomes-a-confused-deputy-vulnerability.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1520,
    "python_slice_tokens": 270,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between *trusting an issuer's signature* and *trusting the issuer's key-resolution path*. A verifier that validates every signature in a cross-issuer chain correctly can still be exploited if it resolves each issuer's public key through a mutable, issuer-controlled discovery document at verification time. The signature check passe...",
    "what_was_observed": "In a reproduction against an AAIF verifier configured with two trusted roots (`issuer-a` and `issuer-b`), a delegation chain was constructed as follows: 1. `issuer-a` signs a root attestation for agent `alpha`, with a `delegates_to` claim naming agent `beta` and declaring `issuer-b` as the attestation authority for `beta`. 2. The verifier, resolving `beta`'s attestation, fetches `issuer-b`'s JWKS from the discovery U...",
    "condition_of_validity": "This boundary is only reachable when all of the following hold simultaneously: - The chain spans two or more distinct issuers, and at least one non-root issuer's key set is resolved dynamically (via discovery document, JWKS URL, or DID document) rather than pinned in verifier configuration. - Key lookup is keyed on a non-unique identifier (`kid`, key thumbpr...",
    "decision_boundary": "The operational rule: **an instance must pin an issuer's key set to the issuer identity before that issuer's link is used to authorize any downstream link, and must never let a dynamically resolved key set shadow a key already bound within the same chain.** Concretely, the verifier must decide, per link, between two mutually exclusive policies: - **Pinned mo...",
    "operational_effect": "When the boundary is respected, cross-issuer delegation remains auditable: every link's authorizing key is traceable to exactly one issuer identity, and a poisoned discovery document can at worst cause a *rejection* (collision → hard fail), never an *acceptance*. When violated, the failure is silent and asymmetric: legitimate chains verify normally, and the ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "004def9d511a3e9d7f902e30e0dc084da12ddb3e07c15e1468749b0246536f3b",
    "verified_classes": [
      "CrossIssuerKeyCollision",
      "AttestationLink",
      "Verifier"
    ],
    "verified_functions": [
      "_resolve_key",
      "verify_chain"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CrossIssuerKeyCollision"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
