2026-08-31T0411Z-intel

Verification & coverage notes

Runaway-duration explanation. This fire's corrected duration_seconds (13655s, ~3.8h) trips the 3h watchdog threshold. The cause is the Phase 5.7 verification loop running its full 8-iteration cap: each of iterations 1-8 returned NEEDS_FIXES (never CLEAN), with genuine, well-evidenced truth-gate and editorial findings on every pass; none of the eight iterations was a wasted or repeated cycle. Phase 0-5.5 (research, composition, the mechanical gate) completed in under an hour; the remaining ~2.8h was entirely the verification loop's sequential remediate-and-re-spawn cycle. Per Phase 5.7's decision rule 6 (cap fail-open), the run published on the 8th iteration's residual findings, 8 of 9 truth+editorial findings remediated before publish, one (a low-moderate-confidence CVE-status hedge on the AI-infrastructure deep dive) declined with a documented rebuttal; verification_residual_count: 8 reflects that no further independent cold pass confirmed the applied fixes, not that they are believed wrong.

Window: gap_hours=15 (previous run: 2026-08-30T1312Z-audit, started 2026-08-30T13:12:06Z), window_hours=24 (24h floor applies), standard-class gap, no catch-up disclosure required.

Coverage backlog worked down (state/coverage_backlog.md). Five open rows from the 2026-08-30 audit were re-gated on today's facts, deep-read from their primaries, and published this run: WatchGuard Fireware OS (new vulnerability entry), Microsoft's TerminalFix campaign (new threat entry), Microsoft's "AI infrastructure becomes the target" report (new threat entry, this run's deep dive; CVE-2026-42271/CVE-2026-48710 already covered by the 2026-06-09 entry are declared in references[]; CVE-2026-49869 is new), Huntress's Famous Chollima/DPRK forensic report (landed as an update record on 2026-08-19/purpledelta-dprk-it-worker-facilitator-rmm-detection; Famous Chollima is an alias this entry already carried, so the reusable PiKVM/Guermok detection methodology extended the existing entry rather than opening a new one), and the Norway/Digdir ID-porten DDoS (new incident entry, direct sector nexus as a public-sector shared-identity-gateway incident, carrying a transferable architectural lesson for Switzerland's own Agov/CH-Login consolidation). Two rows stay open: Boston Scientific (re-checked, still no source names an attacker mechanism) and the inside-it.ch Insel Gruppe lead (escalated, see below).

S3 classifier trip. S3's first attempt terminated immediately with a content-safety classifier trip ("Sonnet 5's safeguards flagged this message"). Retried per this pipeline's documented recovery procedure for classifier-blocked research workers: the reframed instructions dropped inline campaign/cluster names (pointing at the coverage-backlog file instead of enumerating them) and asked for incremental findings-YAML checkpointing. The retry completed cleanly within its 45-min cap. The failed first attempt is not counted in sub_agents.S3 telemetry above, which reflects the successful retry only.

inside-it-ch: now a persistent, not transient, block. Three independent research workers (S2, S3, S4) each attempted inside-it-ch this run, essential-tier, and S2 additionally chased the specific rotation-priority backlog lead (an article on Insel Gruppe/Bern hospital group delaying a ServiceNow migration "wegen eines Sicherheitsvorfalls"). Every transport failed identically across all three: direct GET 403, trafilatura extraction returns no readable body, the jina reader relays an upstream block/challenge, and the RSS path separately returns Cloudflare error 526 (an invalid SSL certificate on inside-it.ch's own origin, not an egress-side block). tools/source_health.py's store-wide sweep confirms HTTP 526 and flags needs-demote. Per the hard rule that a transport block never demotes, the source's tier/status are unchanged; consecutive_fetch_failures was incremented and the finding documented in its notes for the audit. This is now the 3rd consecutive fire fully unreachable, if a 4th also fails, the source needs either a new working transport or an explicit fetch_method: blocked classification.

Borderline-drop: CVE-2026-77956 (ash_ai / Elixir Ash Framework AI extension), unauthenticated CVSS 10.0 RCE with a public working PoC, published today. S1 flagged this as borderline and it was dropped after triage: the ecosystem (Elixir/Ash/Phoenix) is niche with no confirmed Swiss public-sector or supplier deployment, and the underlying pattern (untrusted input reaching an LLM-agent framework's code-evaluation layer) is already well covered in-store by higher-relevance entries (Hugging Face, the Taiwan agentic-AI intrusion, GTIG AVDH, isolated-vm, and this run's own AI-infrastructure deep dive). Doubt about relevance to this constituency resolves toward drop per PD-11's calibration rule.

Essential-coverage: missed=cisa-advisories (persistent 403, reader-credit-exhausted per the source's own notes; the CISA KEV JSON feed substitutes for the exploited-vulnerability surface), cisa-directives (same 403 condition; no corroborating evidence of a new directive from any other source), inside-it-ch (whole-host transport block, 3rd consecutive fire, see above).

Watchlist: not applicable, this deployment configures no product or supplier watchlist (documented no-op; S1 and S4 both reported checked=0/hits=0 as instructed).

Coverage gaps: ssd-disclosure (Cloudflare robot-challenge screen on every transport, no substitute source); helpnetsecurity (homepage is a JS-driven newsletter stub with no article listing, recipe gap, not a transport failure, worth a dated source-notes update); ncc-research (listing HTML did not expose parseable per-post links in the time available, light-effort miss, not pursued given no expected regional signal); google-tag (resolves to Google's general security blog, not a TAG-specific dated listing, known recipe gap).

Item-granularity note. The Zéro Logement Vacant breach and the France SDIS data-leak campaign are both new entries despite sharing the actor:zerobytes / French-public-sector-breach theme with existing entries, distinct victim, distinct platform/mechanism and distinct victim class in each case, per the item-granularity rule; none shares a CVE with covered ground.