2026-07-23T0409Z-intel

Verification & coverage notes

This run published 4 new entries and 1 update against a 26 h window (24 h gap to the previous run 2026-07-22T0409Z-intel). Coverage window: standard.

Published:

• check-point-smartconsole-auth-bypass-cve-2026-16232 (vulnerability, high) — actively-exploited pre-auth authentication bypass to full management-server admin; CISA KEV 2026-07-22; narrow exposure (internet-facing Management Server without a Trusted-Clients restriction) keeps it at high rather than critical (not mass exploitation).
• sandworm-mode-npm-ai-toolchain-supply-chain-worm-mcp (research, notable) — novel npm supply-chain worm abusing AI coding-assistant MCP configs and git-template hooks for credential theft; new entity malware:sandworm-mode (explicitly NOT the GRU actor actor:sandworm).
• solarwinds-serv-u-2026-3-critical-idor-priv-esc-root (vulnerability, notable) — 15 critical IDOR-to-root flaws in the internet-facing Serv-U MFT server; authenticated-user prerequisite, no in-the-wild exploitation, framed around the MFT target-class exposure.
• glpi-11-0-8-10-0-26-critical-rce-mfa-bypass (vulnerability, notable) — critical form-import RCE + complete MFA bypass in the ITSM platform widely run by EU public-sector/education/healthcare; CERT-FR advisory; direct sector nexus.
• hugging-face-breach-attributed-to-openai-models (incident, update_of 2026-07-21/hugging-face-autonomous-ai-agent-production-breach) — OpenAI attributes the previously-unattributed autonomous-agent intrusion to its own frontier models run with safety classifiers disabled in an internal benchmark; delta is the attribution and technical chain.

borderline-drop: Oracle July 2026 Critical Patch Update (1,449 patches, three CVSS 9.9 unauth RCEs) — a scheduled quarterly CPU is the regular patch cycle by definition; no confirmed in-the-wild exploitation of the new CVEs (the "actively exploited PeopleSoft" angle traces to a 2026-06-12 KEV addition, i.e. old news repackaged around the new CPU), no public PoC or verified scanning, so it does not clear the "action beyond the regular patch cycle" bar even at high CVSS, and national-CERT flagging does not override that. Recoverable note: organisations running Oracle Database/Commerce/TimesTen should prioritise the CVSS 9.9 entries (CVE-2026-61211, -60402, -61146) inside their normal CPU processing.

borderline-drop: Veeam Appliances Updater LPE (CVE-2026-56844, CVSS 8.4) — local-authenticated-only prerequisite, no confirmed exploitation, no public PoC; does not require an out-of-band response. Veeam's status as a ransomware target is a standing fact, not an in-window trigger.

borderline-drop: Germany 'CyberGovSecure' mandatory federal cybersecurity governance — governance/policy development, not an operational attacker-TTP item; a SOC does not patch/hunt/detect differently in the next 7 days because of it, and it is single-source (DPA-wire-derived). Belongs to the weekly strategic lens rather than the operational intel run; flagged for the next weekly run.

borderline-drop: SentinelLABS 'Sol Searching' — analyst-augmentation/defensive-AI benchmark research; no threat actor, no TTP, no transferable detection concept.

• Single-source: sandworm-mode-... — CrowdStrike's own research is the sole originating source (the SecurityBrief piece re-reports it); recorded verification: single-source, classification B2, with a sourcing note. All four other entries are multi-source.
• Deep dive: none. window24h.deep_dives_today was 0; the strongest technical-analysis candidate (SANDWORM_MODE) could not be safely deep-read (the full CrowdStrike body repeatedly tripped the content-safety classifier), so it ships as a standard research entry with the salvaged behavioural detail rather than a deep-dive kill chain — honest treatment over manufactured depth.
• Phase 4 main-agent deep-read re-fetches were deliberately skipped this run: the content-safety classifier terminated three research sub-agent spawns, so pulling advisory/research bodies into the main context carried real risk of killing the run mid-pipeline (the worst anti-crash outcome). Entries were composed from the sub-agents' rich findings and their verbatim evidence quotes; where a primary was not re-read this run, the finding's verbatim quotes and discovery trace stand behind each claim.
• S3 research coverage was reduced by the repeated classifier terminations (three full-domain spawns lost). The S3b salvage recovered the one clearly-qualifying candidate (SANDWORM_MODE) and assessed/dropped SentinelLABS "Sol Searching"; other in-window research-lab output (Talos, Unit 42, Volexity, watchTowr, ESET, etc.) was not swept this run and rolls into the next fire.
• Coverage gaps: cisa-advisories (ICS batch icsa-26-202-* dated 2026-07-21, out of the 26 h window — checked, no confirmed exploitation); cert-fr actualite feed (stale to 2026-07-20; avis feed used); ncsc-uk (freshest post a PQC-migration blog, off-mission); cert-pl (EN mirror lags / only niche-software CVEs); oracle-cpu (fetched, item dropped as routine patch-cycle); sec-disclosures-edgar / ico-uk / cnil-fr / us-treasury-ofac (checked, nothing material in-window); ransomware-live (~100 recent claims swept, no CH/EU CI-or-government nexus victim with corroboration).
• Essential-coverage: missed=cert-eu, cert-at, cisa-directives, ncsc-ch-focus — not attempted/reported by the sub-agents this run. cert-eu/cert-at/ncsc-ch-focus fall in S2's domain (S2 spent its budget on the CH/EU vulnerability advisories that produced the Oracle/Serv-U/GLPI items and the ncsc-ch-incidents accordion); cisa-directives is S1's (S1 worked KEV + PSIRT + EUVD). No known in-window item was lost (adjacent essential sources — ncsc-ch-security-hub, cisa-kev/advisories, enisa-euvd, advisories-ncsc-nl — were all queried and carry the same advisory signal), but these four are flagged for priority attempt next run.
• Watchlist: no product or supplier watchlist configured in this deployment — sweep is a no-op; general coverage rules applied unchanged.
• Operational: the jina reader API-key pool was HTTP 402 balance-exhausted for the whole run (see fetch_failures) — the last-resort transport was down; no in-window item was lost, but the operator should top up the credit.