CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

2026-11-04T0256Z-intel

One pipeline fire, in full · intel run of 2026-11-04 · sub-agent allocation and telemetry, per-iteration verification verdicts and findings, source-list edits, coverage gaps, bridge invocations, and the run's own verification & coverage notes: what was published, what was dropped at the borderline or judged not relevant (and why), single-source carve-outs, and contradictions. Rendered from runs/2026-11-04/2026-11-04T0256Z-intel.md.

Run telemetry

2026-11-04T0256Z-intel intel prompt v4.24 publish ok
3h 44m duration 4 published 6 updates
Claude Sonnet 5.5 (claude-sonnet-5-5) main agent
S1 Claude Sonnet 5.5 (claude-sonnet-5-5)
Items returned
7
Duration
23m 40s
Tool calls
7 WebFetch9 WebSearch170 bridge
Cited sources
3 of 26 in slice
S2 Claude Sonnet 5.5 (claude-sonnet-5-5)
Items returned
11
Duration
14m 58s
Tool calls
1 WebFetch30 WebSearch110 bridge
Cited sources
2 of 19 in slice
S3 Claude Sonnet 5.5 (claude-sonnet-5-5)
Items returned
13
Duration
24m 09s
Tool calls
0 WebFetch10 WebSearch160 bridge
Cited sources
2 of 26 in slice
S4 Claude Sonnet 5.5 (claude-sonnet-5-5)
Items returned
8
Duration
18m 56s
Tool calls
3 WebFetch18 WebSearch85 bridge
Cited sources
1 of 12 in slice

Verification

✓ double-CLEAN · Sonnet 5.5 ×2 #1 NEEDS_FIXES · Sonnet 5.5 · t=8 e=9 a=5 #2 NEEDS_FIXES · Sonnet 5.5 · t=8 e=2 a=1 #3 NEEDS_FIXES · Sonnet 5.5 · t=1 e=3 a=3 #4 NEEDS_FIXES · Sonnet 5.5 · t=2 e=1 a=2 #5 NEEDS_FIXES · Sonnet 5.5 · t=2 e=0 a=3 #6 NEEDS_FIXES · Sonnet 5.5 · t=1 e=0 a=1 #7 CLEAN · Sonnet 5.5 · t=0 e=0 a=6 #8 CLEAN · Sonnet 5.5 · t=0 e=0 a=6

Deep dive

·

Entries this run published (4) and updated (6)

Sources changed (this run)

Edits this run made to sources/sources.json · promotions, demotions, new candidates, and fetch-method / category / reliability / url corrections (the run record's sources_changed[]). Paginated; 10 per page.

12 last_successful_fetch · 5 notes · 1 rss_url · 1 added.

SourceChangeFrom → ToReason
ncsc-ch-security-hublast_successful_fetch· → 2026-11-04fetched and used
bitdefender-threat-debrieflast_successful_fetch· → 2026-11-04fetched and used
bleepingcomputerlast_successful_fetch· → 2026-11-04fetched and used
heise-seclast_successful_fetch· → 2026-11-04fetched and used
inside-it-chlast_successful_fetch· → 2026-11-04fetched and used
cisa-kevlast_successful_fetch· → 2026-11-04fetched and used
cisa-advisorieslast_successful_fetch· → 2026-11-04fetched and used
anssi-frlast_successful_fetch· → 2026-11-04fetched and used
sentinellabslast_successful_fetch· → 2026-11-04fetched and used
bsi-delast_successful_fetch· → 2026-11-04fetched and used
tagesschaulast_successful_fetch· → 2026-11-04fetched and used
cert-eulast_successful_fetch· → 2026-11-04fetched and used
zimperium-zlabsrss_url· → https://zimperium.com/blog/rss.xmlS3: the feed https://zimperium.com/blog/rss.xml reads directly with dated items
zimperium-zlabsnotes· → recipe note appended2026-11-04 (S3): working feed; extract each post
bitdefender-threat-debriefnotes· → recipe note appended2026-11-04 (S3): Business Insights research now publishes on businessinsights.bitdefender.com/<slug>
kaspersky-securelistnotes· → recipe note appended2026-11-04 (S3): the feed serves English articles under a /tr/ path; extract reads them
sentinellabsnotes· → recipe note appended2026-11-04 (S3): feed reads directly; article extract is served through the reader
nau-chnotes· → recipe note appended2026-11-04 (S3): /news/digital is the productive listing
cert-eu-blogadded· → status: candidateS3: CERT-EU research blog outside the cert-eu advisories record; candidate, reliability A

Coverage gaps (this run)

Sources this run's brief needed that returned no usable content via any documented recipe. Bridge-recovered or quiet-day sources do NOT appear here. (Distinct from the independent source-accessibility probe at the foot of this section, which probes all active sources regardless of what any run needed.)

Source (uncovered)URL triedMethod chainStatus / classWhat the agent did instead
connectwise-trust-centerhttps://www.connectwise.com/company/trust/advisoriesextract → jina → webfetch → websearch403 transport-403
direct 403, trafilatura no readable body, the reader relayed the block and WebFetch answered 403, on the advisories and security-bulletins pages
status.connectwise.com read with extract and the CCCS feed checked for ConnectWise advisories; none in window
ico-ukhttps://ico.org.uk/about-the-ico/media-centre/news-and-blogs/bridge:url-direct → extract → jina → webfetch → websearch403 transport-403
403 on the bridge recipe, extract, the reader and WebFetch for the fourth consecutive run
WebSearch found no ICO enforcement notice dated November 2026; 403 never demotes
sygniahttps://www.sygnia.co/blog/bridge:url → bridge:feed → extract → jina403 transport-403
direct 403 on the page, feed and sitemap, trafilatura no body, the reader relays the challenge
record already pinned blocked; no in-window content obtainable

Bridge invocations (this run)

6 bridge calls this run · these are successful bridge fetches (separate from "Coverage gaps" above).

6 other
  • tools/kev_window_diff.py ×1
  • tools/fetch_source.py cisa-kev ×1
  • tools/fetch_source.py ncsc-csh recent / post ×1
  • tools/fetch_source.py bsi-rss + bsi-csaf ×1
  • tools/fetch_source.py extract (bodies saved under work/<run-id>/bodies/) ×1
  • tools/source_health.py ×1

Verification findings · all iterations

Per-iteration finding detail. Each table is one verifier pass · what was flagged, how the main agent remediated it, and the outcome. Walking the tables top-to-bottom shows the verifier's debugging trail across iterations.

Iteration #1 NEEDS_FIXES · 22 findings (truth=8, editorial=9, advisory=5) · Claude Sonnet 5.5 · 18m 22s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F3
claim-not-supported
·
Barracuda's page says 'If a patch has not been automatically applied, customers should manually apply the appropriate patch' and recommends turning automatic patching on; 'Many devices receive them au·
F3
claim-not-supported
·
The 'Barracuda says ... are less exposed' half comes from Barracuda's Guidance section ('Organizations whose administrative interfaces are not publicly accessible from the internet are less exposed to·
F4
hallucinated-fact
·
Neither Barracuda page names 9.4.0.030: the Trust Center table lists only BNSF-40425 (9.4.017+) and BNSF-40430 (<9.4.017), the Campus article says 9.4.0.029. 9.4.0.030 comes only from the Mandiant-CNA·
F4
hallucinated-fact
·
The cited advisory carries a banner (in its HTML, dropped by the text extraction): 'Updated incident disclosure · 3 November 2026 ... For the latest findings, incident timeline, impact, and recommende·
F4
hallucinated-fact
·
Bitdefender (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack): 'An attempt to remove EDR ... ran on the file server as av_remove.ps1 ... The scripts were aimed at Sophos and B·
F4
hallucinated-fact
·
Cisco hardening advisory (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-esa-dfCrfXkm, rev 1.1 of 2026-10-14): 'These vulnerabilities were found durin·
F4
hallucinated-fact
·
Hardening advisory fixed table (SEG): '15.5 and earlier 15.5.5-014 16.0 Migrate to a fixed release. 16.5 16.5.0-780'. The SQL-injection advisory gives 16.0 -> 16.0.4-302. So upgrading a 16.0 appliance·
F5
missing-citation
·
True (Mandiant CNA record: affected 0 lessThan 9.4.0.030) but no source for it is listed in sources[] or cited inline anywhere in the entry. Cite https://github.com/mandiant/Vulnerability-Disclosures/·
F8
needs-more-research
·
Mandiant's per-vulnerability disclosures (https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0042.md and MNDT-2026-0041.md; reported by Barracuda 2026-10-22 and 2026-10-1·
F8
needs-more-research
·
https://opsshield.com/notice/security-incident-disclosure-servermanage.html (published 2026-11-03): fake update live for about 70 minutes ('If your server had cPGuard installed and online between 02:0·
F8
needs-more-research
·
The same WDR article (https://www1.wdr.de/nrw/cyberangriffe-supermarkt-kuehltruhen-nrw-100.html) reports: 'Die Rewe-Zentrale bestätigte dem WDR, dass es sich um einen Cyberangriff handelte, der sich g·
F8
needs-more-research
·
Bitdefender describes, and the entry omits: finance-share files staged into registry values under HKLM\SOFTWARE and sent by HTTP POST to a page on the attacker's unmanaged host ('The registry-as-trans·
F9
surface-contradiction
·
The new section presents a direct confirmation to watson.ch (watson: 'Wie die Bundesanwaltschaft bestätigt, steckt eine berüchtigte Erpresserbande dahinter ... Und nun hat sie den aktuellen Fall hinzu·
F9
surface-contradiction
·
(low confidence) The new section cites Ivanti's CNA record (CVE-2026-118527 fixed by 25.1.1.3 and 22.8R2.6, https://cveawg.mitre.org/api/cve/CVE-2026-118527) and CERT-FR ('Ivanti précise que les versi·
F11
editorial-advisory
·
Removing the KEV-deadline clause left 'the same day, and flagging it' ungrammatical, and the blank line between the 'Two details' paragraph and 'The same day, Cisco shipped ...' was lost, so the two r·
F11
editorial-advisory
·
Bitdefender's own mapping table adds T1555.003, T1059.006, T1021.002, T1021.006, T1078.002, T1036, T1074, T1112, T1105, T1041, T1053.005, T1490 (all active in the pinned dataset); the clearly describe·
F11
editorial-advisory
·
(low confidence) The body section says no source names the equipment or ties the case to the Danfoss and Copeland controllers; the summary (and the record summary) place it beside the Danfoss wave wit·
F11
editorial-advisory
·
check_run's _main_words counts 737 before and 737 after on the refrigeration entry (git HEAD vs working tree); 'cut from 737 to 738' is also self-contradictory. State 737 to 737.·
F11
editorial-advisory
·
(low confidence) The Binance entry has a paragraph saying why the access chain transfers; this entry says nothing about why a Swiss public-sector SOC should read it (a hosting or web-server estate run·
F12
single-source-flag-missing
·
(low confidence) The note itself says the sources are one assessor; either set a single-source value (vendor primary; NCSC-CH is on the carve-out list) or add the independent Mandiant CNA records (htt·
F14
quantifier-without-source
·
(low confidence) Bitdefender: 'Every attacker action we saw originated there.' The qualifier is dropped, turning an observation limited to its telemetry into an absolute.·
F18
action-item-discipline
·
(low confidence) Hedged and not executable as written: Barracuda's patch table lists patch ids (BNSF-40425 for 9.4.017+, BNSF-40430 for earlier), not the 9.4.0.029/9.4.0.030 builds, so the reader cann·

Iteration #2 NEEDS_FIXES · 11 findings (truth=8, editorial=2, advisory=1) · Claude Sonnet 5.5 · 22m 20s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·
The pages do carry a date: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0042.md has '## Disclosure Timeline * 2026-10-22: Reported by Barracuda * 2026-11-02: CVE pu·
F4
hallucinated-fact
·
Hardening advisory (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-esa-dfCrfXkm, rev 1.1) says only 'Two of them are known to be actively exploited. F·
F3
claim-not-supported
·
The cited page (cisco-sa-hardening-esa-dfCrfXkm) carries only the revision table ('1.1 Added link to a related advisory. Summary and Details Final 2026-OCT-14; 1.0 Initial public release. - Final 2026·
F4
hallucinated-fact
·
Both cited CERT-FR pages now read 'Connect Secure (ICS) version 25.1.2.x antérieures à 25.1.3.1' (https://www.cert.cyber.gouv.fr/avis/CERTFR-2026-AVI-1442/ and https://www.cert.ssi.gouv.fr/alerte/CERT·
F4
hallucinated-fact
·
The cPGuard summary still carries the superseded advisory account; the vendor's disclosure (https://opsshield.com/notice/security-incident-disclosure-servermanage.html) says the attacker 'signed up as·
F4
hallucinated-fact
·
Stale after remediation. The rewritten Barracuda entry does carry the CVE-record mechanism (Mandiant MNDT-2026-0042 and -0041 as sources, and 'invoke a configuration-import function and restore a craf·
F3
claim-not-supported
·
The disclosure says 'Change the root password and every local user password on the server.' The qualifier 'from a trusted recovery environment' is in the earlier advisory (https://opsshield.com/notice·
F3
claim-not-supported
·
Bitdefender recommends 'Put an endpoint agent on every machine. The staging host here was unmanaged' and 'Restrict remote execution and administrative shares ... Limit them to known management hosts.'·
F8
needs-more-research
·
Iteration 1 asked for the version bounds; the run record says the page text read did not carry them, but the cited Mandiant record does (raw https://raw.githubusercontent.com/mandiant/Vulnerability-Di·
F9
surface-contradiction
·
The earlier advisory frames the exposure as versions 5.88.12 to 5.88.19 with example install_log lines running from 02:46 to 12:46 on 02-11-2026 ('detected the attack within 12 hours'), while the disc·
F11
editorial-advisory
·
States the access step as established; the vendor's own text says 'Our logs do not record the exact request that gave them access' (its timeline lists the crafted requests at 22:50 and command executi·

Iteration #3 NEEDS_FIXES · 7 findings (truth=1, editorial=3, advisory=3) · Claude Sonnet 5.5 · 20m 21s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·
(low confidence) The vendor hedges: https://opsshield.com/notice/cpguard-update-channel-compromise.html says 'A successful update removes the known files, but credentials copied before cleanup may sti·
F9
surface-contradiction
·
(low confidence) The SQL-injection advisory (cisco-sa-esa-inj-2bLVGmhX) says 'This vulnerability was found during the resolution of a Cisco TAC support case.' The hardening advisory (cisco-sa-hardenin·
F9
surface-contradiction
·
(low confidence) The same CERT-FR alert page (updated 2 Nov) now lists 'Connect Secure (ICS) version 25.1.2.x antérieures à 25.1.3.1' and says 'Ivanti précise que les versions 25.1.3.x ne sont pas aff·
F5
missing-citation
·
(low confidence) The clause describes what the 2026-11-03 disclosure states and omits, but the only citation in the paragraph is the earlier advisory; https://opsshield.com/notice/security-incident-di·
F11
editorial-advisory
·
The Exposure check repeats Campus's 9.4.0.029 threshold while the action and takeaway tell the reader to reach 9.4.0.030 (the Mandiant record lists 9.4.0.029 as affected). A reader who stops at the Ex·
F11
editorial-advisory
·
Bitdefender's ATT&CK table (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack) also maps T1490 (wbadmin delete systemstatebackup), T1555.003 (Chrome Login Data copy), T1059.006,·
F11
editorial-advisory
·
(low confidence) The advisory page's own dateline is '<time datetime="2026-11-03">3 November 2026</time> ... Last updated 3 November 2026, 3:19 AM IST (UTC+05:30)', and BleepingComputer (2026-11-03) s·

Iteration #4 NEEDS_FIXES · 5 findings (truth=2, editorial=1, advisory=2) · Claude Sonnet 5.5 · 19m 05s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·
Cisco's SQL-injection advisory (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-inj-2bLVGmhX) says only 'This vulnerability was found during the resolution o·
F3
claim-not-supported
·
(low confidence) The cited Volexity page says 'Ivanti is tracking both the RCE and authentication bypass components of this chain under CVE-2026-104935.' The CVE binding is right; the verb's subject i·
F17
classification
·
(low confidence) Reliability A rests on OPSSHIELD's own incident notices; OPSSHIELD is not a record in sources/sources.json (no A tier), the two notices disagree on scope (32 retrieved files and versi·
F11
editorial-advisory
·
(low confidence) Bitdefender says 'a new trust between domains is a rare change and cheap to alert on' of the trust only; for domain-admin accounts it says to put them 'behind change control, and aler·
F11
editorial-advisory
·
Carry-over advisory from iteration 3 (T1490 and T1555.003 are now added). Bitdefender's own ATT&CK table (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack) still lists T1059.00·

Iteration #5 NEEDS_FIXES · 5 findings (truth=2, editorial=0, advisory=3) · Claude Sonnet 5.5 · 17m 18s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F3
claim-not-supported
·
(low confidence) heise (https://www.heise.de/news/Cyberangriffe-auf-Kuehlschraenke-Erste-deutsche-Faelle-in-Bayern-und-NRW-11508922.html) says 'In einem Supermarkt im niederbayerischen Reisbach sind d·
F4
hallucinated-fact
·
(low confidence) The advisory (https://opsshield.com/notice/cpguard-update-channel-compromise.html) itself calls the 32 files 'a preliminary estimate of confirmed data retrieval, not the total number ·
F11
editorial-advisory
·
(low confidence) Bitdefender's sentence is 'The registry-as-transport channel is an unusual choice and a strong indicator to hunt for' and refers to the registry transport (results and files staged in·
F11
editorial-advisory
·
Carry-over from iteration 4, left as is by the main agent. Bitdefender's ATT&CK table (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack) still lists T1059.006 (portable Python ·
F11
editorial-advisory
·
(low confidence) The disclosure (https://opsshield.com/notice/security-incident-disclosure-servermanage.html) says the script 'collected sensitive files and sent them to a server the attacker controll·

Iteration #6 NEEDS_FIXES · 2 findings (truth=1, editorial=0, advisory=1) · Claude Sonnet 5.5 · 12m 22s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F4
hallucinated-fact
·
The count is stale after the iteration-5 remediation. check_run._main_words (the gate's own function, link text only, main analysis above the first update section) gives 737 at git HEAD and 736 in the·
F11
editorial-advisory
·
Carry-over, left as is by the main agent and may be left. Bitdefender's ATT&CK table (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack) still lists T1059.006 (portable Python r·

Iteration #7 CLEAN · 6 findings (truth=0, editorial=0, advisory=6) · Claude Sonnet 5.5 · 18m 01s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F11
editorial-advisory
·
(low confidence) Cisco's hardening advisory (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-esa-dfCrfXkm) says 'multiple internally discovered vulnera·
F11
editorial-advisory
·
(low confidence) cves[CVE-2026-20353].type is 'dos', but Cisco's table describes CWE-664 as 'covers uncontrolled resource consumption, algorithmic complexity, recursion/iteration, deserialization, and·
F11
editorial-advisory
·
(low confidence) actions[2]: the advisory (cisco-sa-esa-inj-2bLVGmhX) says 'Cisco has directly contacted customers who own Cisco Secure Email Cloud devices where indicators of possible compromise were·
F11
editorial-advisory
·
(low confidence) The Wordfence Intelligence page (https://www.wordfence.com/threat-intel/vulnerabilities/id/4b4da0cf-d9f4-47c4-a0e8-6c4dc5a6f250) shows 'Publicly Published October 28, 2026' and 'Last ·
F11
editorial-advisory
·
(low confidence) Bitdefender (https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack) writes 'Veeam', 'the backup software's databases' and links the vendor's 'vbr_rest' REST documen·
F11
editorial-advisory
·
Carry-over advisory from iterations 4 to 6, left as is by the main agent and may be left: Bitdefender's ATT&CK table still lists T1059.006 (portable Python running crackw.py), T1021.006 (backdoor acco·

Iteration #8 CLEAN · 6 findings (truth=0, editorial=0, advisory=6) · Claude Sonnet 5.5 · 17m 33s

F-codeSectionItem · URL/quoteVerifier summaryRemediation · outcome
F11
editorial-advisory
·
(low confidence) Carry-over of iteration 7, pre-existing wording. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-esa-dfCrfXkm says 'multiple internall·
F11
editorial-advisory
·
(low confidence) Carry-over of iteration 7. The advisory (cisco-sa-esa-inj-2bLVGmhX) says 'Cisco has directly contacted customers who own Cisco Secure Email Cloud devices where indicators of possible ·
F11
editorial-advisory
·
(low confidence) Carry-over of iteration 7. The page's dateline reads 'Publicly Published October 28, 2026 | Last Updated October 31, 2026'; the CVE record's datePublished is 2026-10-31T05:33Z. The la·
F11
editorial-advisory
·
(low confidence) Carry-over advisory of iterations 4 to 7, left as is by the main agent. https://businessinsights.bitdefender.com/3am-ransomware-hybrid-ai-attack maps these four ids (portable Python c·
F11
editorial-advisory
·
(low confidence) A victim-published count of its own blocked cases (https://www.binance.com/en/blog/community/3229153443759566763: 'detected and prevented 57 suspected North Korea-linked cyber threat ·
F11
editorial-advisory
·
(low confidence) The 'unauthenticated remote attacker ... configuration-import' wording is Mandiant's (MNDT-2026-0042); Barracuda's own table (https://trust.barracuda.com/security/pre-authentication-a·

Verification & coverage notes

The run record's narrative body, verbatim. This is where the run accounts for its own judgement calls: every borderline drop and judged-not-relevant item with its reason, dedup decisions, single-source items and their carve-outs, contradictions, and per-source coverage gaps, so nothing the run considered disappears silently.

Verification & coverage notesrun record body

2026-11-04T0256Z-intel · Sonnet 5.5 · window 26 h · 4 entries published

Verification & coverage notes

Coverage window: standard (gap 24.0 h, previous run 2026-11-03T0256Z-intel; window 26 h; the 24.003 h gap is daily-cadence jitter, not an outage, so no outage-backfill sweep). Four new entries and six changelog records (5 update, 1 improvement); no deep dive (no candidate met the bar), no critical. The four new entries are Barracuda ESG (CVE-2026-116606 and CVE-2026-111560, notable), the cPGuard update-channel compromise (notable), Binance's own account of the 2026-10-29 theft (notable) and the 3AM affiliate intrusion into a UK school estate (notable).

Changelog records. update: CISA's KEV listing of CVE-2026-119977 on the WordPress core entry (the mechanical sweep's one COVERED-STALE row; priority notable to high); Cisco's re-release of the 15.5.5-014 fix and revision 1.2 on the Secure Email Gateway entry (critical stays; the exploit-code statement is Cisco's alone, and the pre-existing KEV-deadline wording in that entry was removed under the zero-warning rule, with immediate_action declared on the record); the arrest of a 16-year-old pupil on the Vaud school entry; the German cases, SentinelLABS' "responsibility not established" assessment and Le Canard enchaîné's blood-service cold-room report on the refrigeration entry (main analysis 737 words before and 736 after, so no growth; the entry stays over the 550 bound and is a candidate for the audit's trim); PKZH's suspended migration, PK Softech's non-pseudonymised-data statement and the Federal Prosecutor's addition of the case to its Akira proceeding on the Publica entry (the analysis is 1,148 words after 1,158, so it was not grown, the superseded PKZH sentence was rewritten in place). improvement (no float): CVE-2026-118527's CNA record and CERT-FR's confirmation that Ivanti calls all three chain flaws exploited, on the Ivanti Connect Secure entry.

KEV disposition. CVE-2026-119977 (COVERED-STALE) shipped as the update above; no RANSOMWARE rows and no NOT COVERED or MENTION-ONLY rows. Backlog. ARX Group SA / Aurora and the ChimeraZ commune claims were re-checked by S2 and S4: no victim, client, regulator or Swiss-press confirmation, so both stay held under their stated conditions (expiry 2026-11-07 and 2026-11-17) and no note was appended.

Source tension. Barracuda's Campus page names firmware 9.4.0.029 as the gateway fix while the CVE record lists builds before 9.4.0.030 as affected; the entry states both and resolves neither, and the mechanism and the per-product affected ranges come from Mandiant's per-vulnerability disclosures (the EUVD record returned an application-unavailable page). The vendor table calls CVE-2026-116606 pre-authentication while listing administrative access as the requirement, as NCSC Switzerland points out. cPGuard's earlier advisory estimate (32 retrieved files) and the spokesperson's 2,946 servers are kept only in the sourcing note, superseded by the vendor's later disclosure (about 2,950 servers and about 7,900 billing-portal accounts). The blood-service report rests on one weekly (Le Canard enchaîné); the 110 degrees is a programmed set-point. A composed BSI/Apple mercenary-spyware entry was withdrawn before the gate to match the 2026-11-03 incident-floor drop (see below).

  • borderline-drop: Control Web Panel CWP2Shell (ten VulnCheck CVEs, unauth chain to root, fixed 1.29), no constituency nexus established, no exploitation, niche hosting panel; marginal niche disclosure
  • borderline-drop: HPE Networking Fabric Composer HPESBNW05172 (46 CVEs, three 9.6-9.8), fix in regular cycle, no exploitation, no exposure-driven urgency, no constituency nexus
  • borderline-drop: Zyxel GS1900 CVE-2026-107441 and AP/FWA7 CVE-2026-76955, LAN-adjacent only (AV:A), no exploitation; regular patch cycle
  • borderline-drop: Kaspersky CyberStrikeAI (LLM orchestrator on the C2, education sector in Africa and Latin America), published 2026-11-02 08:00Z, outside the window; no constituency nexus; LLM-operated intrusion already covered (ARTEX, VAPOR PANDA, the 3AM entry)
  • borderline-drop: CERT-EU AI-agent harness backdoor lab experiment, lab experiment, no in-the-wild use; the in-the-wild analogue (Cursor marketplace extension) is covered
  • borderline-drop: GTIG/Mandiant LLMjacking, stolen cloud tokens drive fraudulent LLM spend, no constituency nexus; generic cloud-identity detection; unresolved CVE-2026-40217 mapping
  • borderline-drop: GTIG XCPE Android set-top-box botnet takedown, consumer/IoT residential-proxy botnet, no constituency nexus, no new decision for a SOC
  • borderline-drop: ESET APT Activity Report Q2-Q3 2026 (PD-9 periodic report), periodic recap; highly relevant findings already covered (UAC-0099/Sandworm entry); no Swiss-public-sector nexus; only the summary page read
  • borderline-drop: ESET Gorbag (Ukraine law-enforcement/defence targets), Ukraine-only victims, WinRAR CVE-2025-8088 already covered
  • borderline-drop: Team Cymru Cl0p second edition, planning-grade pattern recap of covered campaigns (first published 12 Aug, updated October), no new finding
  • borderline-drop: Check Point prompt adware (Codex jailbreak bundle), dual-use adware-style bundle, no constituency nexus
  • borderline-drop: WorkOS internal sales-app breach (ARTEX named by founder), CRM/support data only, no access path stated, no constituency nexus; ARTEX is already tracked
  • borderline-drop: Holcim confirms data theft, Emperador claim (~360 GB), incident floor: no access vector, actor behaviour or transferable lesson beyond the impact; private company
  • borderline-drop: Ukraine and Russia emergency-alert apps hacked (false nuclear warnings), already dropped on 2026-11-03; no vector, AP primary not read; no new fact in window
  • borderline-drop: Swiss GitLab exposure count (Inside IT relaying Shadowserver: 48 instances on CVE-2026-110264, 8 also on CVE-2026-97229), single secondary source, exposure count changes no action on an entry that already tells reader to patch now
  • borderline-drop: SiK-N motion 26.4717 (digital dependencies in procurement), a submitted parliamentary motion, no obligation or deadline for the constituency
  • borderline-drop: Federal Council transitional authorisation model for e-evidence to EU authorities, obligation concerns Swiss providers' legal handover, no defender-side consequence for the constituency
  • borderline-drop: BACS week 44 review (Plex and home-network compromises), private home networks, no public-sector nexus; Plex2Shell KEV date rests on search snippets
  • borderline-drop: Vaud CYBER26 crisis exercise 2026-11-12, an exercise invitation, not threat intelligence
  • borderline-drop: Zimperium Coruna/DarkSword chains by iOS version (update-of DeadTag), no change to the patch decision, the entry already tells readers to update iOS
  • borderline-drop: Android November bulletin (Framework RCE CVE-2026-58868 Critical), Chrome 157, Dell DSA-2026-416, Juniper JSA112183, Canonical LXD CVE-2026-112816, no exploitation reported or outside the window; regular patch cycle
  • borderline-drop: Amadeus breach, hold condition (Swiss or European carrier confirmation) unmet
  • borderline-drop: BSI: Apple mercenary-spyware threat notifications to Bundestag and government members (Apple: 99 countries), dropped on 2026-11-03 under the incident floor and nothing materially new in window beyond Apple's reach statement: no vector, actor or behaviour is public and no ATT&CK id is evidence-bound; the BSI guidance is individual-device hygiene and no source states a Swiss recipient or Swiss authority statement (composed as an entry in this fire, then withdrawn before the gate to stay consistent with the incident floor)

Source health: 291 probed; 287 relevant, 1 stale, 3 unreadable, every non-relevant record already handled (action breakdown 291 none), so no repair order was open. One new candidate, cert-eu-blog (S3: CERT-EU's own research blog outside the cert-eu advisories record); recipe notes added for zimperium-zlabs (working RSS feed set), bitdefender-threat-debrief, kaspersky-securelist, sentinellabs and nau-ch. extract fell back to the metered reader for the EUVD, CISA alert, Binance, FBI, SentinelLABS and Le Canard enchaîné pages in the deep read (eight reader calls: the three EUVD records, the CISA alert, Binance, FBI, SentinelLABS and Le Canard enchaîné); no WebFetch was needed by the main agent. The rotation ranked on the cursor (recent_attempts exclusion count 0, the cursor already spreads the pool).

Coverage gaps: ico-uk (403 on every transport, fourth run), connectwise-trust-center (403 on every transport; status page read), sygnia (blocked), rapid7-research (feed not well-formed, outside the slice), lab52 (SSL EOF, outside the slice), ox-security (feed lists dated items, bodies 403, lead-only), edoeb-ch-press (stale listing). Completeness note for the next audit: the 14-day prior-coverage index was loaded in full for its first 40 records and as an id/headline/CVE/entity/last-development projection for the remaining 47 to keep the main context compositional (the sub-agents read the whole file).

Operator note: an early command of this fire used a stale run id and overwrote three tracked files in work/2026-W26-b78503e7/ (prior_coverage.json, prior_coverage_keys.json, state-summary.json) in the working tree; they are not staged and are not part of this commit (restore with git checkout -- work/2026-W26-b78503e7/).

Verification. Eight iterations. Iteration 1 returned NEEDS_FIXES (22 findings, two truth-class rewrites: the cPGuard entry was rebuilt around the vendor's fuller 2026-11-03 disclosure, and the Barracuda entry around Mandiant's per-vulnerability records); iterations 2 to 6 closed the remaining truth findings (the iteration-2 spawn was lost to a container restart and respawned with the same scope; iteration 3 left 18 claims unanswered and was followed by a pass that covered them); iteration 7 returned CLEAN and the cold, full-scope confirmation pass of iteration 8 (231 of 231 claims) returned CLEAN, so the entries publish on a confirmed double-CLEAN with no residual truth or editorial finding. The advisory items left open, all low confidence: four Bitdefender-mapped technique ids unmapped on the 3AM entry, "five further internally-found vulnerabilities" counting CVE ids on the Cisco entry, Cisco's "proactively contacted" wording, the Wordfence Intelligence citation date on the WordPress entry, the 57-case figure's victim-statistic character on the Binance entry, and the attribution of the mechanism sentence in the Barracuda summary. Improvements noticed and not needed this fire, for the next audit: the refrigeration (736 words) and Publica (1,148 words) analyses are far over the 550-word bound and want a trim; a quality-audit pass could add OPSSHIELD to sources/sources.json.

Gate note: the one remaining source-urls warning is the two Mandiant disclosure pages on github.com answering 403 to the gate's own link check (a UA filter); the main agent and the verifier read both through extract and the raw files.

← Operations dashboard · run-record contract: docs/pipeline.md