A Seven-Day Threat Window
This cycle covered July 14 through July 20. The pipeline collected 262 high-signal vulnerability records from 12 sources: 10 newly listed CISA Known Exploited Vulnerabilities, 252 high or critical NVD records, the Go Vulnerability Database, and 10 editorial or specialist research feeds. All 16 Go security modules, the Rust sidecar, and the core engine were introspected before the threat set was compared with current behavior.
The generated manifest proposed 11 actions. Source and test review removed duplicate recommendations for controls that already exist, including Linux inotify monitoring, bounded Safetensors headers and tensor offsets, overlapping Rust scans, and Java, PHP, and Pickle deserialization patterns. The implementation pass concentrated on three current gaps with direct evidence and a clear owner in the existing architecture.
Agentic Dataset Pipelines Became an Initial-Access Surface
Hugging Face disclosed a July production intrusion driven end to end by an autonomous agent system. The initial access path combined a remote-code dataset loader with template injection in dataset configuration, then escalated from a processing worker into credential access and lateral movement. That incident made dataset metadata and loader configuration a runtime security boundary, not just build input.
Data Poisoning Guard now inspects bounded dataset_config, loader_config, config, content, and raw event data for executable Jinja-style templates and Python or process-execution primitives. It separately flags configurations that enable remote dataset code. The change also fixes event routing for the canonical training_update and dataset_update types, which were declared by the module and event schema but were not previously dispatched to the data-update handler. Clean inert dataset metadata remains accepted.
WebSocket Lengths Are Validated Before Inspection
ZDI's CVE-2026-13308 disclosure showed how malformed WebSocket framing could become remote code execution through an integer underflow in an exposed device service. The Rust packet path already enforced SSH payload limits and scanned deep binary content, but it did not understand RFC 6455 frame boundaries.
The sidecar now records confirmed plaintext HTTP Upgrade flows by client and server address and port, then validates subsequent client frames without allocating from attacker-controlled lengths. It rejects reserved bits and opcodes, unmasked client frames, non-canonical 16-bit and 64-bit lengths, fragmented or oversized control frames, the forbidden high bit, and payload claims above 16 MiB. Unconfirmed binary flows are not interpreted as WebSocket traffic, which keeps the rule precise.
The Existing BYOVD Control Learned QMUDisk
CVE-2026-15515 identified a vulnerable Tencent PC Manager QMUDisk driver. Runtime Watcher already detects driver-load telemetry and blocks a maintained set of signed vulnerable drivers commonly abused to disable security tooling or gain kernel access.
The existing blocklist now includes qmudisk64.sys, with regression coverage alongside RTCore64, Process Explorer, Huawei, Gigabyte, and Intel driver cases. This is a focused intelligence refresh inside Runtime Watcher; it does not add a feed client, background service, or seventeenth module.
A Dependency Match Was Not a Reachable Vulnerability
The module inventory matched golang.org/x/crypto v0.52.0 to GO-2026-5932. The official advisory applies specifically to the unmaintained openpgp packages, covers all versions, and names no fixed release. 1SEC neither imports those packages nor calls their symbols. Direct govulncheck analysis reports zero reachable vulnerabilities, zero vulnerabilities in imported packages, and one advisory present only in the required module graph.
The correct response was not an invented upgrade to a nonexistent fixed version. The weekly pipeline now records govulncheck reachability alongside OSV matches and instructs its review stages to reject module-only remediation and unsupported target versions. This keeps dependency inventory useful without turning every transitive match into release churn.
v0.4.22 Also Aligns Runtime Reporting
The release includes the runtime and cloud-reporting alignment completed after v0.4.21. The CLI and cloud heartbeat now share the compiled release version, cloud ingest URLs are joined safely when the configured base contains a trailing slash, correlation metadata is type-checked before reporting, and enforcement records are marked sent only after a successful upload so failed reports can retry.
The public engine remains one Go binary with 16 security modules and an optional Rust sidecar. No runtime dependency or security module was added. Downloads, checksums, signatures, and provenance are available from the [v0.4.22 GitHub release](https://github.com/cutmob/1-SEC/releases/tag/v0.4.22).
Verification
Focused tests cover malicious executable dataset templates, remote loader enablement, clean dataset configuration, canonical event routing, qmudisk64.sys driver loads, confirmed WebSocket upgrades, extreme 64-bit frame lengths, valid masked frames, and unconfirmed binary traffic.
The complete public Go package set passed race-enabled tests under Go 1.26.5, build, vet, gofmt, Staticcheck, Gosec, govulncheck, and OSV scanning. The Rust sidecar passed formatting, Clippy with warnings denied, all 192 tests, dependency audit, Linux all-feature CI with libpcap, and an optimized v0.4.22 build. The release workflow builds six Rust targets and the signed multi-platform Go artifacts before publishing downloads.