2026-08-24T0410Z-intel

Verification & coverage notes

This fire ran 4 h 47 min behind itself before it did any research. The container stalled between preparation and the start of research — the run's own start stamp reads 04:10:43Z while the four research workers did not begin until 08:54–08:55Z — so the wall-clock watchdog was already tripped before a single source was fetched, without a minute of research time having been lost. The run was landed under that constraint: the research stage was allowed to finish because it had only just started and was the run's entire research surface, but no scope was widened afterwards, no research was restarted when one domain died, and composition ran in a single pass. The duration_seconds recorded above is the honest wall clock and is not a measure of work performed.

The stall had one fortunate consequence. Switzerland's federal cyber authority published its half-year threat report under an embargo lifting at 09:00 UTC, and the coverage-backlog row for it existed precisely because both the weekly that surfaced it (research window closed 01:15 UTC) and this scheduled fire (nominal start 04:10 UTC) were expected to miss it. The stall put the research window on top of the publication instead. The home-region research was re-tasked mid-flight and caught the report minutes after it went live, and it became this run's deep dive.

Coverage gaps. The research and investigative-reporting sweep did not happen. That work was terminated about twelve minutes in by a content-classifier trip rather than by its time cap, so it wrote no findings file and its domain — vendor and independent threat-research labs, OT/ICS research, investigative reporting — has no sweep behind it this run. It was deliberately not restarted, because the watchdog forbids starting new research that far past the start, and because six of this run's seven published entries are research-domain material worked from the coverage backlog and re-verified directly against the primaries. This is a real hole in the window's completeness and is recorded as one, not softened: genuinely new research published on 2026-08-22 to 2026-08-24 by a lab outside those six primaries would not have been seen. The other gaps are transport, and all seven are logged in full above. Seven sources remain reachable only through the metered reader, whose pool is exhausted on all seven keys — which is what blocked the Spanish national CERT and the vulnerability-disclosure programme behind a standing backlog row, and what left two client-rendered regulator listings unread.

Coverage gaps: cisa-advisories (403, ninth consecutive run, all transports incl. reader); cisa-directives (403, eighth consecutive run); siemens-productcert-csaf (403, partial CSAF-mirror substitute); ssd-disclosure (empty body, reader-only source, pool exhausted); ccn-cert-es (reader-pinned, pool exhausted); ico-uk (200 but client-rendered, reader needed); ncsc-uk (200 but page shell, ladder not exhausted under wall-clock pressure); research-domain sweep (terminated by a classifier trip — no sweep performed).

Essential-coverage: missed=ncsc-uk (client-rendered listing, structured recipe not attempted before that work returned), cisa-advisories (403 on every transport), cisa-directives (403 on every transport).

This fire was overtaken, and the window was re-deduplicated on sync. Three other fires landed on main while this one sat mid-pipeline through a container stall and an account session limit. The 2026-08-24T0906Z-intel fire published the Cisco Secure Workload and Crosswork critical tail — the very item this run had recorded as a coverage-backlog row because it failed only the recency gate — so that row was struck before it was ever committed. More consequentially, the long-delayed 2026-08-22T0410Z-intel fire finally landed its own treatment of the SOCRadar FTP-banner dead-drop research, which this run had also composed from the same primary. That entry was dropped rather than published alongside the earlier one: same source, same event date, no material delta, and the earlier treatment is the fuller of the two. The entity namespace was reconciled the same way — the earlier fire had registered the two malware families as malware:e4del and malware:pinhole-rat, and this run's proposed malware:pinhole would have been a second key for a family that already had one, so it was removed before commit rather than becoming a duplicate the registry would have to tombstone later. The third overtake cost a second entry on the same grounds. The 2026-08-23T1311Z-audit fire's own retrospective truth pass had independently reached the same finding about Red Hat's product-state table for the Keycloak account-takeover flaw and published its correction as 2026-08-24/cve-2026-18963-keycloak-no-red-hat-product-unfixed, so this run's correction of the same record for the same CVE was dropped rather than published beside it. One fact from this run's own parse of that data is not carried by the surviving entry and is not being lost: the vendor's machine-readable product-state document for the flaw was revised on 2026-08-20, the day after this store's erroneous entry was written, which bears directly on the surviving correction's statement that there is no evidence the product state ever read differently. That is a fact about how this pipeline erred rather than something a defender acts on, so it is recorded as a correction owed on the surviving entry in state/coverage_backlog.md and left for the weekly audit to weigh, not published as a third entry on one CVE. What this run published is therefore seven entries, not the nine it composed. The same sync also revealed that main had independently gained a PDF-extraction recipe in the fetch bridge, better than the one written here (it selects on content type, tries mirrors, and distinguishes an image-only PDF from an empty one), so this run's version was discarded in favour of it and only the carve-out host-list fix was kept.

What was published, and why seven. Six of the seven entries clear the backlog the weekly stand-down of 01:10Z handed over — items that fire had already researched, deep-read and quote-verified but could not publish. Backlog rows are exempt from the recency gate because each was verified in-window by the fire that surfaced it and its age reflects a pipeline race rather than staleness; every one was still put to the relevance gate on today's facts and deduplicated against the fourteen-day index. Working that queue down is why this window is longer than the day's genuinely-new signal would suggest, and it is not volume inflation: the alternative was a silent hole, which is exactly what happened to the nine verified items a weekly stand-down listed on 2026-08-03 and never published. One of the seven is a mechanism update on ground the store already holds. A second correction — of a published error of this pipeline's own that overstated exposure on a CVSS 9.1 unauthenticated account-takeover flaw, and could have led a reader to defer it as unpatchable — was composed here and then dropped, because another fire had reached and published the same correction while this one was mid-pipeline; the fix is in the store either way.

Two entries carry a sourcing caveat worth restating here because both were near-misses for a fabricated link. The ShieldBreak mechanism entry ties its research to CVE-2026-69414, but the research names no CVE anywhere — re-confirmed this run by a case-insensitive search of the freshly fetched page body — so the linkage is this pipeline's reading of two accounts of the same named technique and the entry says so rather than implying the researcher made the connection. The ReliaQuest entry began as a piece about a circulating compromise claim set against the victim's own account of what happened, and the review pass established that its only cited source never mentions that claim at all — no extortion brand, no listing, no screenshots. Everything the source would not bear was removed rather than propped up with a weaker second source, so what publishes is the victim's own disclosure and the control lesson in it; the entity key was renamed for the same reason.

Entity-overlap decisions, confirmed deliberate. Two of this run's entries share entity keys with earlier in-window coverage and were still published as new entries rather than deltas; both calls were made knowingly. The half-year report entry links the Dream Job campaign key, which also appears on the 2026-08-12 entry about a Windows zero-day used by a state actor and on a weekly synthesis piece — but this entry is not a development in that campaign, it is the first coverage of a national authority's periodic report, whose Dream Job chapter contributes something neither earlier entry could: Swiss case counts, Swiss loss figures and the authority's own reporting-behaviour finding. Making it an update of a zero-day entry would have buried the report. The SilkParasite entry shares its campaign key with two 2026-08-23 weekly synthesis entries that name the cluster in passing; neither is an operational entry about it, none of its five newly named malware families was registered, and the reusable detection formulation appears in neither — so this is first dedicated coverage, not a delta, and the strategic-to-operational direction is the one the division of labour permits.

Single-source items and carve-outs. Every one of the seven entries is single-source, which is unusual for this pipeline and is stated plainly rather than smoothed over: this window's publishable signal was, almost entirely, individual parties reporting their own work or their own incident. Exactly two carry a carve-out value. The half-year report entry is single-source-national-cert — BACS is the disclosing authority for its own assessment and the report was minutes old, so no independent pickup existed; where it relies on another party's work (the Polish CERT's incident analysis and Static Tundra attribution, a vendor's Teams help-desk research, a national test institute's photovoltaic study) the entry attributes it there rather than to BACS. The ReliaQuest entry is single-source-victim. The remaining five are plain single-source: the ShieldBreak mechanism, SynkLoader, the Rapid7 quarterly, the AWS-key measurement and SilkParasite. One carve-out boundary was tested and got recorded wrong here before it was caught, and is worth restating because the entry that carried it was the one later dropped as a duplicate: a vendor's own product-security team is a first-party authority on its own products, but it is not one of the two carve-outs the policy defines — a national CERT or government authority for its own jurisdiction, and a victim's own disclosure — so vendor-only sourcing is plain single-source, never a carve-out. Each of the five carries its limitation in its own note rather than borrowing confidence from corroboration it does not have.

One internal tension in the half-year report is carried in the entry rather than resolved: its management summary describes reporting as having stabilised at a high level, while its first chapter states the voluntary total as a decline against the prior year's figure. Both are the report's own statements and the entry says so.

Borderline drops.

• borderline-drop: Berlin Landesnetz compromise — fifth consecutive fire blocked on the same ground. The home-region research was tasked to establish one thing only: whether any named authority has since stated an access vector, product or CVE. None has, and the sole vector-adjacent claim in circulation is still an unattributed broadcaster characterisation. An incident entry needs an evidence-bound technique mapping and there is no attacker behaviour to map; inventing one is the defect class a prior audit repaired. The backlog row stays open.
• borderline-drop: Cisco Secure Workload / Crosswork critical tail — eight critical flaws, five at CVSS 10.0, which the W34 weekly roll-up itself flagged as covered by no earlier fire. Relevant and uncovered, but the underlying disclosure is dated 2026-08-19/21 with no in-window delta, so it fails recency for a fresh item today. Recorded as a coverage-backlog row so a later fire publishes it as first coverage rather than losing it.
• borderline-drop: CVE-2026-16242, Red Hat OpenShift / HyperShift Konnectivity proxy — an unauthenticated path into the control-plane-to-node channel, CVSS 9.4, fixed in 4.22.8, and never given a dedicated entry. Dropped on recency: published 2026-07-20 with the vulnerability database's dateUpdated bump being a resync rather than new disclosure. Also recorded as a backlog row.
• borderline-drop: Zoom annotator buffer overwrite CVE-2026-53413 — out-of-window (primary sources 2026-08-11 to 2026-08-20), no in-window delta, dropped despite an eye-catching name.
• borderline-drop: DJI consumer drone CVEs, a Turkish smart-meter authentication bypass, a GNU gzip local decompression overflow — off-scope for this constituency: physical-proximity or local vectors, no exploitation, no evidenced European public-sector or critical-infrastructure deployment.
• borderline-drop: Japanese domestic-market product advisories — fresh but with no evidenced Swiss or European deployment base.
• borderline-drop: three leak-site-only listings naming one Swiss and two German organisations — fake-news guard: attacker assertions with no victim, regulator or high-reliability corroboration.
• borderline-drop: five vendor OSS-mirror CVE records published 2026-08-23 — exploitation and public-disclosure fields both null, no action beyond the regular patch cycle.

Out-of-window drops. out-of-window: Cisco Secure Workload / Crosswork tail — primary source 2026-08-19/21, window_hours=24. out-of-window: CVE-2026-16242 — primary source 2026-07-20, window_hours=24. out-of-window: CVE-2026-53413 — primary source 2026-08-11, window_hours=24.

A note on the version recorded above. prompt_version says v3.31 because that is the prompt this fire actually read and executed. While it was mid-pipeline an overtaking fire bumped the master prompts to v3.32, so the changelog on main now leads this record by one version. The gate's cross-check treats a trailing version as a versioning-rule breach — a prompt edit shipped without its changelog entry — and flagged it, which in this case would only have been "fixable" by claiming to have run a version this fire never saw. The check was therefore taught the distinction rather than satisfied with a false value: it now compares the working tree's prompts against origin/main, and a trailing version reports as informational when this run edited no prompt or agent definition. A genuine prompt edit shipped without a changelog bump still fails exactly as before.

State and tooling. Two tooling defects were fixed rather than logged for later. The half-year report's PDF as first fetched was corrupted — 2,840,294 bytes of mangled content against 1,733,418 bytes on a clean binary re-fetch — and every PDF library in this container fails to import because the pre-installed cryptography package is missing its _cffi_backend binding; stubbing that broken import chain made all 23 pages extractable, which is why the deep dive is composed from the report body rather than its press release. Both worked, so the deep-dive entry rests on the primary. The PDF workaround was then made permanent rather than left as a run anecdote: tools/fetch_source.py gained a pdf <URL> recipe that fetches in binary, refuses a non-PDF body with a clear message, survives a single unreadable page and raises a distinct error on an image-only document, verified against the same 23-page report. That closes the half of the standing Siemens S7 backlog row which asked for a working extraction path to be recorded in the bridge — a row opened because the 2026-08-20 run had to compose a five-agency advisory single-source from an outlet's reading for want of exactly this. It is deliberately NOT yet referenced from the research agents' fetch-tooling section: that would be an agent-definition edit, which must ship a banner bump across all three master prompts, a CHANGELOG entry and a byte-identical regeneration of the alternate verifier in the same commit, and this run is too far past its watchdog to take that on safely. The recipe is discoverable via --help and is recorded in .claude/memory/source-fetch-blocks.md, which every future fire loads; a run with headroom should do the definition edit. The source-health sweep probed 191 of 191 sources in 127 s and returned no unsolved repair order, which is consistent with the three recipe corrections this run made rather than deferred: a reader-pinned source proven reachable by the cheapest transport, and both Swiss authority records moved off a transport their site migration broke.

Watchlist: the organization profile configures no product and no supplier watchlist, so both sweeps were no-ops and neither agent spent time on them.