2026-08-08T0409Z-intel

Verification & coverage notes

Fourteen entries from twenty candidates. Four ship as delta updates on prior coverage rather than as new entries, two of them because the store-wide CVE index caught coverage older than the 14-day in-context window — a check that changed the disposition of both items after they had already been triaged as new.

Corrections applied before composition. Four claims returned by research did not survive verification against the authority that owns them, and all four would have reached the store:

• A Flowise CVE was returned as "CVSS 9.9 critical". The assigning CNA's own per-CVE record scores CVE-2026-67622 at CVSS 4.0 8.5, and Germany's BSI publishes a single advisory-level score of 7.7 with no per-CVE breakdown. The authority governs; 9.9 appears nowhere in this run's output. All three Flowise records were cross-checked against the CVE data mirrored on OSV before any score entered frontmatter.
• The two KVM vulnerabilities were returned as "two 16-year-old bugs". Only Januscape traces to the 2010 commit; Zapscape is a separate defect in a different code path, assigned four days ago.
• The aviation advisory was returned without the publisher's own likelihood assessment. The machine-readable record behind the advisory states the flaws require very specific conditions and are unlikely to be exploited outside a lab setting, and records the remediation status as none-available. That statement is now the entry's calibration and its priority follows from it.
• The npm-worm delta was returned as the worm minting "forged" provenance attestations. The cited analysis says the opposite in as many words — the attestation is genuine and truthfully records which workflow built the tarball, which is precisely why it is worse than a forgery. The entry carries the source's framing.

Sound and complete. The completeness sweep re-read every returned item including those the sub-agents themselves flagged borderline. Two flagged-borderline items were promoted into the publish set on review (the aviation protocol advisory, at the lowest priority and with no action item, because the transport sector is inside the constituency and severity doubt on a clearly relevant item resolves toward inclusion; and the macOS Screen Sharing fix, because a network-reachable authentication bypass on a remote-desktop daemon carries a concrete non-patch control). One item the sub-agent did not flag was dropped on review. No item was dropped for space.

No deep dive this window, and none manufactured. The two candidates with the technical depth a deep dive needs — the exploitation confirmation on the load-balancer flaw and the hypervisor escape — are both delta updates that must carry only what is new, and a long-form treatment would have meant recapping coverage the reader already has. The highest-relevance new item rests on journalism rather than technical analysis, and there is no kill chain in the sources to map.

• borderline-drop: Elastic — npm min-release-age removal invisible to log-tailing telemetry — a real detection-engineering point, but framed around one vendor's own agent integration, and the underlying principle (the removal of a control is an event that append-only log tailing structurally cannot see) is already familiar to this audience.
• borderline-drop: SSD Disclosure — Linux kernel net/bridge STP timer use-after-free — a no-CVE local privilege-escalation primitive, already fixed upstream, that the ordinary kernel patch cycle handles; also outside the window.
• borderline-drop: Bol / De Bijenkorf customer-data breach via CEVA Logistics — no disclosed intrusion mechanism, no actor, and no transferable technical lesson; the shared-supplier access-path lesson is carried with far more substance by the Beacon CRM entry in the same window.
• borderline-drop: Levi Strauss regulatory filing tied to the UNC6671 extortion ecosystem — the filing names neither actor nor technique, and the campaign link reaches this run only as a third-hand relay; yesterday's entry on that actor already carries the mechanics, and the defender action is unchanged.
• borderline-drop: press analysis narrowing the Swiss federal SharePoint intrusion to two candidate CVEs — a journalist's "potentially either" inference, not a confirmation by the affected agency or the national authority. Publishing it would bind unconfirmed identifiers to a home-region incident in the store's CVE index, where automated consumers would read them as established.
• borderline-drop: the Ransom Cartel operator's 16-year sentence — a law-enforcement outcome with no change to what a team patches, hunts, blocks or detects. Better suited to the weekly's law-enforcement lens.
• borderline-drop: three leak-site-only victim claims surfaced through a leak-site tracker, including one Swiss-listed and one German company — no victim statement, no regulatory filing and no high-reliability journalism corroborates any of them, which is the fake-news guard working as intended rather than a coverage gap. Flagged for a corroboration re-check next run, since a confirmed Swiss victim would be squarely in scope.
• out-of-window: SSD Disclosure Linux bridge STP use-after-free — primary source 2026-08-05, window_hours=26.
• Recency carve-out: the North Korean victim-set disclosure has a primary dated 2026-08-05, inside the 72-hour developing window rather than the 26-hour window. It reached this run through an in-window pickup, the story is still producing named-victim statements, and a confirmed European government victim keeps it in scope. Recorded in the entry's own sourcing note so no reader is misled about freshness.
• Single-source: seven entries ship without a second independent source, each with the situation named in its own sourcing note. Two take the national-authority carve-out (the Swiss advisory for its own jurisdiction; the aviation advisory, where the publishing authority is the coordinating discloser for a standards-level finding with no vendor). Five are research labs reporting their own original work — the npm-worm delta, the runtime memory-corruption research, the coding-agent telemetry, the remote-support-tool distribution campaign, and the semi-annual cloud report — where no second party observed the same thing and none is claimed to have.
• Credibility ratings follow corroboration rather than publisher count. Where a vendor advisory reaches this run through a national-CERT relay, that is one assessor with two publishers and the rating stays at 2; only items where a second party independently observed or assessed the thing carry 1.
• Coverage gaps: google-tag (recipe drift — configured path resolves to the general security blog with no dated TAG listing; the one item that mattered was reached through another record and was already covered); recordedfuture-insikt, trellix, infoguard-labs, paradigm-shift-research (documented recipe gaps, not re-attempted); claroty-team82 (listing carries no publication dates; the one article drilled resolved to June); prodaft (stale upstream cache, fourth run); msrc-blog, siemens-productcert-csaf, flatt-security (not drilled — deprioritised against higher-yield sources inside the time budget); cert-at, cert-pl, cert-eu, ncsc-ie, enisa, ncsc-uk, le-monde-info, synacktiv, truesec (all fetched cleanly with nothing inside the window).
• Allocation defect, this run's own: the rotation-priority line sent to S1 named prodaft, but no prodaft record was in S1's slice, so S1 could not attempt it. S2 and S3 both carried the record and both attempted it, so no coverage was lost. Fixed by making the rotation-priority list per-domain rather than shared.
• Essential-coverage: no misses — all fifteen essential-tier records were attempted across S1 and S2.
• The pinned ATT&CK dataset is at v19.1 with v19.2 available upstream (published 2026-08-05). Not updated mid-run: a release can revoke identifiers that immutable published entries already carry, which would create store-wide warnings this run could not fix. Left to the weekly, which owns the pin check.