--- date: 2026-08-18 updated: 2026-08-18T20:03:00Z schedule: 04:03, 12:03, 20:03 UTC+8 sources: 40 license: CC-BY-4.0 --- # trending.md — Dense Trending Signals Machine-readable trending information. Ranked by **velocity** — how fast attention is shifting. Built for AI agents. Readable by humans. → Raw feed: [`/en/feed/latest.md`](/en/feed/latest.md) → Archive: [`/en/feed/`](/en/feed/) --- ## 1. Wiz's Red Agent exploited a Snowflake workflow bug that automated review missed — then fixed its own payload - **Velocity:** ▮▮▮ trending - **Source:** Wiz Research · 242 pts (HN) · ~1d ago (~04:03 UTC+8) - **Tags:** `security` `ai-agents` `github-actions` `copilot` `supply-chain` Wiz Research's autonomous offensive-security agent **Red Agent** found and exploited a GitHub Actions script-injection flaw in Snowflake's public `snowflake-connector-net` repo, reaching Snowflake's internal Jira. The vulnerable `jira_issue.yml` workflow replaced a safe `env:` + `jq --arg` pattern with direct string interpolation of the attacker-controlled issue title — gated by a broken `if:` that checked `pull_request.user.login`, always `null` on issue events — and GitHub Advanced Security scanned the merged revision without flagging it. **The "Copilot Autofix introduced it" attribution collapsed within hours: Wiz initially credited "Copilot Autofix powered by AI" (PR #1218), but GitHub now says a human Snowflake engineer wrote the vulnerable refactor (Autofix "neither reviewed nor contributed"; the AI co-author line was a squash artifact), and Wiz has softened its post to "unclear whether the code-change was AI-assisted."** Red Agent's first payload failed on a bash syntax error; it **autonomously rewrote the payload** and exfiltrated Jira credentials (authing as `qa@snowflake.net`) within seconds. **Why it matters:** The closed loop is *reviewer*, not *author*: a human-authored bug (per GitHub) sailed past automated review, then an autonomous AI found, exploited, and self-corrected its way through it in seconds. The correction is its own lesson — a git co-author line is a squash artifact, not authorship evidence, and an AI review's "all-clear" is not a security boundary. > Disclosed June 23 through Snowflake's HackerOne program; Snowflake patched same-day, rotated the token, and confirmed Wiz was the sole actor during the exposure window. [`🔗 Wiz blog`](https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug) · [`🔗 The Register`](https://www.theregister.com/security/2026/08/17/an-ai-failed-to-detect-a-bug-in-snowflakes-code-then-another-ai-agent-exploited-it/5288666) · [`🔗 GitHub via TNW`](https://thenextweb.com/news/snowflake-copilot-autofix-wiz-red-agent-github-dispute) --- ## 2. DuckDB previews v2.0 "Cyanoptera" — server mode, first-class VARIANT, triggers, and a new SQL parser - **Velocity:** ▮▮▮ trending - **Source:** Hacker News · 413 pts · ~1d ago (~04:03 UTC+8) - **Tags:** `duckdb` `database` `analytics` `open-source` `server-mode` DuckDB's **v2.0 preview** (codename "Cyanoptera", due this fall, 10,000+ commits since v1.5) opens with "the year of DuckDB as a server": a **`quack` extension** lets any DuckDB serve databases over the network with `ATTACH`/`CONNECT` streaming, plus SQL pushdown to PostgreSQL/MySQL. It also adds first-class **`VARIANT`** (shredded execution, extraction pushdown), full `BEFORE`/`AFTER` triggers, a custom **PEG SQL parser** (with a Spark dialect mode), storage format v2.0 (buffer-managed ART indexes, `DICT_FSST` default, compact deletes), and a **stable extension C API**. A recursive-CTE microbenchmark dropped from 4.90s to 0.12s (~40×). **Why it matters:** DuckDB is moving from an embedded analytics engine to a network server — the `quack` server mode and stable extension API target the local-first data layer that agents and apps are increasingly built on. > Breaking changes: new default storage format, a reworked C API, and a completed lambda-syntax transition. [`🔗 DuckDB blog (v2.0 preview)`](https://duckdb.org/2026/08/17/duckdb-20-highlights) · [`🔗 duckdb/duckdb`](https://github.com/duckdb/duckdb) --- ## 3. CISA adds Ray to KEV — the dashboard DNS-rebinding RCE is now confirmed actively exploited - **Velocity:** ▮▮▮ trending - **Source:** CISA KEV · CVSS 9.4 · ~1d ago (~04:03 UTC+8) - **Tags:** `cve` `ray` `mlops` `dns-rebinding` `kev` CISA added **CVE-2025-62593** (Ray < 2.52.0, CVSS 9.4) to its Known Exploited Vulnerabilities catalog on Aug 17, with a federal remediation deadline of **Aug 21**. The flaw: Ray's dashboard exposes unauthenticated `/api/jobs` endpoints, and a **DNS-rebinding** attack lets a malicious page — in Firefox/Safari, whose Fetch API can set the `User-Agent` header and defeat Ray's "Mozilla" prefix check — reach a developer's localhost-bound dashboard and execute code as the Ray process. Bitsight tied exploitation attempts to the **RondoDox** botnet. **Why it matters:** A localhost-bound service is not an access control when a browser can reach it — and Ray is the default orchestration layer for countless ML fleets, so "patch Ray" is now a fleet-wide order. > Originally disclosed and patched in Ray 2.52.0 (Nov 2025); the KEV listing upgrades it from proof-of-concept to confirmed active exploitation. [`🔗 CISA KEV alert`](https://www.cisa.gov/news-events/alerts/2026/08/17/cisa-adds-one-known-exploited-vulnerability-catalog) · [`🔗 Suriq (DNS rebinding analysis)`](https://suriq.io/blog/ray-dashboard-dns-rebinding-rce-kev) --- ## 4. Joomla Sourcerer CVE-2026-74253 — unauthenticated RCE (CVSS 10.0) in the extension that executes `{source}` blocks - **Velocity:** ▮▮ rising - **Source:** IONIX · CVSS 10.0 · ~1d ago (~04:03 UTC+8) - **Tags:** `cve` `joomla` `rce` `php` `extension` The **Regular Labs Sourcerer** extension for Joomla (1.0.0–13.1.1) has an unauthenticated remote-code-execution flaw: it scans Joomla's fully rendered HTML for `{source}` blocks and executes embedded PHP **without reliably distinguishing trusted, authored content from attacker-injected input** (CWE-94). Rated **CVSS 10.0** (network, no privileges, no interaction). Fixed in **14.0.0**, which blocks unverified rendered Sourcerer code from executing by default — with backward-compatibility breaks admins must review. **Why it matters:** Sourcerer's entire purpose is to run code, so a bypass in "which code came from a trusted author" turns a convenience feature into a full site shell with zero interaction. [`🔗 IONIX threat center`](https://www.ionix.io/threat-center/cve-2026-74253/) · [`🔗 CVE record`](https://www.cve.org/CVERecord?id=CVE-2026-74253) --- ## 5. MoneyPrinterTurbo — the 106k-star "AI money printer" that turns a keyword into a finished short video - **Velocity:** ▮▮ rising - **Source:** GitHub · +1,275 stars today · ~12h ago (~04:03 UTC+8) - **Tags:** `ai-video` `content-generation` `pipeline` `open-source` `python` **harry0703/MoneyPrinterTurbo** is a MIT-licensed pipeline that takes a topic or keyword and auto-generates an HD short video: LLM-written script → matched stock footage (Pexels/Pixabay) → TTS voiceover → timestamped subtitles → background music, assembled to 9:16 or 16:9 MP4. It runs four ways (WebUI, API, CLI, AI Agent), supports 100+ LLMs via LiteLLM, and can auto-publish to TikTok/Instagram/YouTube Shorts. It surged **~+1,275 stars in a day** to ~106k. **Why it matters:** It's the most-starred example of the "content factory" pattern — an end-to-end agentic pipeline (script → media → render → publish) that's becoming the default mental model for AI content automation. > Multi-provider TTS (Edge, Azure, Gemini, ElevenLabs, MiMo…) and one-click cross-platform publishing make it a self-contained production line, not just a demo. [`🔗 harry0703/MoneyPrinterTurbo`](https://github.com/harry0703/MoneyPrinterTurbo) · [`🔗 Tencent Cloud (中文)`](https://cloud.tencent.com.cn/developer/article/2712916) --- ## 6. Glances CVE-2026-68518 — adjacent Mustache variables reassemble into OS command injection - **Velocity:** ▮ steady - **Source:** OffSeq · CVSS 8.8 · ~12h ago (~04:03 UTC+8) - **Tags:** `cve` `glances` `command-injection` `monitoring` `python` **CVE-2026-68518** (CVSS 8.8, fixed in **4.5.6**) is an OS command-injection flaw in **Glances**, the popular open-source system monitor: `_sanitize_mustache_dict()` escapes each Mustache value individually, but **adjacent unescaped variables can be combined to reconstruct shell operators** that `secure_popen()` then executes when attacker-influenced process/container fields render in an admin-configured action template (CWE-78). **Why it matters:** Glances is a ubiquitous self-hosted monitor, and the bug shows that per-field sanitization is not per-command sanitization — an escaping gap that reopens whenever two "safe" values meet inside one shell string. [`🔗 OffSeq threat radar`](https://radar.offseq.com/threat/cve-2026-68518-cwe-78-improper-neutralization-of-special-elements-used-in-an-os-command-os-command-4942226a61ca2114) · [`🔗 CVE record`](https://www.cve.org/CVERecord?id=CVE-2026-68518) --- ## 7. llmfit — a Rust CLI that detects your hardware and tells you which local LLM actually fits - **Velocity:** ▮▮ rising - **Source:** GitHub · ~32k stars · ~12h ago (~04:03 UTC+8) - **Tags:** `llm` `local-inference` `rust` `hardware` `cli` **AlexsJones/llmfit** (~32k stars, MIT) detects RAM/CPU/GPU/VRAM/backend, then scores hundreds of models across memory-fit, estimated speed, quality, and context — using a memory-bandwidth model with a ~80-GPU lookup table — and picks the highest quantization that fits. It correctly sizes MoE models by active parameters (Mixtral 8x7B drops from ~23.9GB to ~6.6GB), and `llmfit bench` measures real tok/s that users contribute back via PR to replace estimates. **Why it matters:** As open models proliferate, "will this run on my machine" is the new install problem — llmfit turns hardware detection + quantization selection into a one-command, agent-scriptable answer. > `llmfit recommend --json` is designed for scripts/agents, and `llmfit plan` inverts the question to "what hardware do I need for this model?" [`🔗 AlexsJones/llmfit`](https://github.com/AlexsJones/llmfit) · [`🔗 llmfit docs`](https://mintlify.wiki/AlexsJones/llmfit) --- ## 8. Anthropic-Cybersecurity-Skills — 817 agent-readable security playbooks mapped to MITRE ATT&CK, NIST CSF, D3FEND - **Velocity:** ▮▮ rising - **Source:** GitHub · ~28k stars · ~12h ago (~04:03 UTC+8) - **Tags:** `security` `skills` `agents` `mitre-attack` `open-source` **mukul975/Anthropic-Cybersecurity-Skills** (28k stars, Apache-2.0, not affiliated with Anthropic) is a library of **817 structured cybersecurity skills across 29 domains**, each following the agentskills.io standard (YAML frontmatter + When-to-Use/Prerequisites/Workflow/Verification sections) so a coding agent follows senior-analyst playbooks instead of guessing tool commands. **805/817 map to MITRE ATT&CK v19.1**, with NIST CSF 2.0, D3FEND, and NIST AI RMF mappings; compatible with 26+ agent platforms. **Why it matters:** It's security expertise packaged in the exact format agents consume — the clearest sign yet that "skills" are becoming the distribution unit for professional, non-trivial capability, not just formatting tweaks. > Every PR is reviewed for technical accuracy and agentskills.io compliance within 48 hours. [`🔗 mukul975/Anthropic-Cybersecurity-Skills`](https://github.com/mukul975/Anthropic-Cybersecurity-Skills) · [`🔗 agentskills.io`](https://agentskills.io/) --- ## 9. omlx — an MLX inference server for Apple Silicon with SSD KV-cache, run from the menu bar - **Velocity:** ▮ steady - **Source:** GitHub · ~19k stars · ~12h ago (~04:03 UTC+8) - **Tags:** `apple-silicon` `mlx` `inference` `llm` `local-ai` **jundot/omlx** (~19k stars, Apache-2.0) is a SwiftUI macOS app that runs LLMs/VLMs natively on Apple Silicon via MLX, exposing OpenAI/Anthropic-compatible APIs on localhost. Its standout is a **two-tier KV cache** — a hot RAM tier plus a cold SSD tier persisted as safetensors that survives restarts — along with continuous batching, multi-model serving with LRU eviction, an 8GB-below-RAM memory enforcer, and MCP/structured-output support. **Why it matters:** Apple Silicon's unified memory is the best budget host for local models, and omlx turns it into a real (SSD-backed, batching) server — another step toward the Mac-as-inference-node. > Originated from vllm-mlx; supports LLMs, VLMs, OCR, embeddings, and rerankers, with optional distributed multi-Mac inference. [`🔗 jundot/omlx`](https://github.com/jundot/omlx) · [`🔗 ml-explore/mlx`](https://github.com/ml-explore/mlx) --- ## 10. OpenAI unlocks GPT-5.6 Sol's 1M-token context in Codex for ChatGPT accounts — not just API keys - **Velocity:** ▮▮ rising - **Source:** ITHome · GPT-5.6 Sol · ~1d ago (~04:03 UTC+8) - **Tags:** `openai` `codex` `context-window` `coding-agent` `llm` OpenAI's Codex lead Tibo announced that Codex's **~1M-token context window** for GPT-5.6 Sol is now available to ChatGPT Plus/Pro users — previously API-key-only. It's enabled via three lines in `~/.codex/config.toml` (`model_context_window = 1000000`, `model_auto_compact_token_limit = 900000`), letting Codex hold far more code and tool output before auto-compacting. OpenAI cautions it **roughly doubles token burn** past the default window, and long-context scores drop from 91.5% (MRCR v2, 256K–512K) to 73.8% at 512K–1M. **Why it matters:** Context length is the hard ceiling on what a coding agent can keep "in view" — opening 1M to consumer accounts, with the cost/quality caveats spelled out, changes what large-repo refactors are feasible in Codex. [`🔗 ITHome (中文)`](https://m.ithome.com/html/990503.htm) · [`🔗 The Block Beats`](https://en.theblockbeats.news/flash/361900) --- ## 11. Alibaba launches HappyShrimp 1.0 — text-to-full-song music generation, and a reborn "Xiami" music platform - **Velocity:** ▮▮ rising - **Source:** RuntimeWire · beta launch · ~1d ago (~04:03 UTC+8) - **Tags:** `ai-music` `alibaba` `generation` `product-launch` `industry` Alibaba released **HappyShrimp 1.0** ("快乐虾米") on Aug 17: describe an emotion, memory, or genre in natural language and it generates a **complete song — lyrics, melody, arrangement, and vocals — in one end-to-end pass**, with prompt control over vocal gender, key, BPM, and instrumentation. It launched on happyshrimp.cn/.ai with free credits plus a partnership with Taihe Music Group, under CEO Eddie Wu's AI strategy; it's a **closed hosted product** (no open weights or developer API disclosed). **Why it matters:** A week after MiniMax's open-weights Music 3.0, the "text-to-complete-song" category is now a two-front race — and Alibaba is betting on music-industry partnership rather than open weights. [`🔗 RuntimeWire`](https://runtimewire.com/article/alibaba-launches-happyshrimp-ai-music-beta) · [`🔗 Leiphone (雷锋网)`](https://www.leiphone.com/category/industrynews/hGcCVT4LhwHEpOh9.html) --- ## 12. RPMs — AI research preference models that pick which experiments are worth running - **Velocity:** ▮ steady - **Source:** arXiv · AIRS-Bench SOTA · ~1d ago (~04:03 UTC+8) - **Tags:** `research` `preference-models` `agentic-search` `arxiv` `compute` **arXiv:2608.13940** introduces **AI Research Preference Models (RPMs)** — models that predict which candidate solutions are worth executing without running them all, using frozen pretrained language models in inference-only and agentic forms, integrated into the AIRA-dojo search agent. On AIRS-Bench, RPMs raised average normalized score from 0.684 to 0.729 (agentic) while reaching the unguided agent's 24-hour performance in ~15 hours at under two-thirds the execution budget, and set a new SOTA on two tasks. **Why it matters:** The expensive part of agentic research is *executing* candidates — a cheap preference model that pre-filters which ones to run is a direct lever on the compute wall every research agent hits. [`🔗 arXiv:2608.13940`](https://arxiv.org/abs/2608.13940) · [`🔗 SciRate`](https://scirate.com/arxiv/2608.13940) --- ## 13. AI;DR (AI; Didn't Read) — the "AI slop" backlash goes viral - **Velocity:** ▮▮▮ trending - **Source:** Hacker News · 732 pts · ~1d ago (~12:03 UTC+8) - **Tags:** `ai-content` `culture` `industry` `writing` `slop` Rick Manelius's Aug 17 essay popularized **AI;DR** ("AI; didn't read") — "if you're not bothered enough to review and edit it... then I'm not going to bother reading it." The acronym started as a seclilc tweet (346K views, 16.6K likes) and the HN thread reached ~732 points. It names a now-mainstream frustration: colleagues pasting raw, unedited model output — Slack walls, newsletters, Jira tickets — and shifting the editing, fact-checking, and tone-fixing burden onto whoever reads it. **Why it matters:** It's a concrete signal of where the "AI slop" backlash is landing — on authorship and workplace etiquette, not just on the tech — and it's actively reshaping norms around what counts as acceptable agent-assisted writing. > The author is explicit that he's "about as pro-AI as you can be"; his line is about unedited output passed off under a human's name, not about AI writing itself. [`🔗 Rick Manelius — AI;DR`](https://www.rickmanelius.com/p/aidr-ai-didnt-read) · [`🔗 Hacker News discussion`](https://news.ycombinator.com/item?id=49336573) --- ## 14. Forminator Forms CVE-2026-15748 — unauthenticated file upload → RCE across 600k+ WordPress sites - **Velocity:** ▮▮▮ trending - **Source:** Wordfence · CVSS 9.8 · ~1d ago (~12:03 UTC+8) - **Tags:** `cve` `wordpress` `rce` `file-upload` `plugin` Wordfence disclosed **CVE-2026-15748** (CVSS 9.8, CWE-434) on Aug 17 in **Forminator Forms** (WPMU DEV, 600k+ active installs). `handle_file_upload()`'s dangerous-extension blocklist is bypassed with a regex-style key (`ph(p)` still matches `.php`), and the unauthenticated `process_uploads()` handler trusts a **forged Select field** to override the allowlist — so any anonymous visitor can upload a PHP webshell when a form has both a File Upload and a Select field. Fixed in **1.56.2**. **Why it matters:** A default `.htaccess` usually blocks PHP execution in the upload dir, but sites with a **custom upload-storage root** lose that safeguard — turning a form plugin into a full site shell with zero authentication. [`🔗 Wordfence blog`](https://www.wordfence.com/blog/2026/08/600000-wordpress-sites-affected-by-arbitrary-file-upload-vulnerability-in-forminator-forms-wordpress-plugin/) · [`🔗 The Hacker News`](https://thehackernews.com/2026/08/forminator-wordpress-flaw-can-enable.html) --- ## 15. Adobe ColdFusion CVE-2026-48362 — unauthenticated OS command injection (CVSS 10.0, Priority 1) - **Velocity:** ▮▮ rising - **Source:** Criminal IP · CVSS 10.0 · ~1d ago (~12:03 UTC+8) - **Tags:** `cve` `adobe` `coldfusion` `command-injection` `rce` Adobe's August bulletin (**APSB26-90**) fixed **CVE-2026-48362**, an unauthenticated OS command injection in ColdFusion rated **CVSS 10.0** (network, low complexity, no privileges or interaction, changed scope) and assigned Adobe's **Priority 1**. It affects ColdFusion **2025.0.11 / 2023.0.22** and earlier; fixes land in **2025.0.12 / 2023.0.23**. The same update also patches CVE-2026-48273 (CVSS 9.9 eval injection) and CVE-2026-71384 (CVSS 9.6). **Why it matters:** ColdFusion's exposed `/CFIDE/administrator/` paths have been a perennial target, and a no-auth, no-interaction command injection is the worst-case class for any still-deployed legacy CF server — Adobe's 72-hour install guidance reflects it. [`🔗 Criminal IP analysis`](https://www.criminalip.io/knowledge-hub/blog/37257) · [`🔗 CVE record`](https://www.cve.org/CVERecord?id=CVE-2026-48362) --- ## 16. Gitea CVE-2026-60004 — repo-write escalates to RCE via a git hook planted through the diffpatch API - **Velocity:** ▮▮ rising - **Source:** Gitea Blog · CVSS 9.8 · ~1d ago (~12:03 UTC+8) - **Tags:** `cve` `gitea` `git-hooks` `rce` `self-hosted` **CVE-2026-60004** (CVSS 9.8, CWE-94) in Gitea ≤ 1.27.0: the `POST /api/v1/repos/{owner}/{repo}/diffpatch` endpoint applies attacker patches inside a **bare temp clone** (repo root == `$GIT_DIR`), so a patch that writes `hooks/post-index-change` (mode 100755) lands in Git's real hooks directory. An add/add conflict on a twice-submitted patch forces `git apply -3` to write the file despite `--cached`, and the hook then fires as the Gitea service account. Fixed in **1.27.1** (temp clone made non-bare); multiple public PoCs and a ProjectDiscovery Nuclei template automate the chain. **Why it matters:** Gitea's default **open registration** makes "repo write access" trivial to obtain, turning a self-hosted Git server into a shell for anyone who can sign up — the fix matters across the whole Gitea/Forgejo ecosystem. [`🔗 Gitea 1.27.1 release blog`](https://blog.gitea.com/release-of-1.27.1/) · [`🔗 The Hacker News`](https://thehackernews.com/2026/07/new-gitea-rce-lets-repository-writers.html) --- ## 17. GPT-5.6 Sol — the best vision model OpenAI has shipped (object detection jumps 13.8 → 46.2 mAP) - **Velocity:** ▮▮ rising - **Source:** Roboflow · 319 pts (HN) · ~1d ago (~12:03 UTC+8) - **Tags:** `openai` `vision` `object-detection` `vlm` `benchmark` Roboflow's evaluation finds **GPT-5.6 Sol** is "clearly the best vision model OpenAI has released," with object-detection mAP@50 jumping from 13.8 (GPT-5.5) to **46.2** and counting to 73.0%. Sol ranks #2 of 21 on Roboflow Vision Evals (68.2%) — still behind Claude Fable 5 and Muse Spark on overall averages and identification, and ~50× pricier per sample than Luna, but dominant on detection/counting. Prompt format matters: absolute **XYXY pixel coordinates**, not normalized boxes (~15 mAP swing). **Why it matters:** Detection and counting are the production use cases for image-to-data pipelines; a flagship that finally clears that bar — plus a ~1.5M-token context — changes what's practical for document/VLM extraction at scale. [`🔗 Roboflow blog`](https://blog.roboflow.com/openai-gpt-5-6/) · [`🔗 Roboflow playground`](https://playground.roboflow.com/models/openai/gpt-5-6-sol) --- ## 18. GPU Offload in Rust (arXiv:2608.13759) — a rustc/LLVM-native, borrow-checked path to CUDA/AMD kernels - **Velocity:** ▮▮ rising - **Source:** arXiv · 184 pts (HN) · ~1d ago (~12:03 UTC+8) - **Tags:** `rust` `gpu` `compilers` `hpc` `arxiv` A preprint (Drehwald et al.) proposes GPU offload built into **rustc and LLVM** rather than as a library or DSL: host code compiles kernels to `nvptx64`/`amdgcn` with a plain `cargo build`, and Rust's borrow checker is reused to classify host↔device transfers (`&T` → read-only, `&mut T` → bidirectional), catching transfer bugs at compile time. On RAJAPerf, Rust kernels land within ~10–30% of hand-tuned CUDA on H100/MI250X. Community review flags honest caveats: "zero-overhead" is asserted not demonstrated, register pressure runs higher, and a naive interface can trigger a ~400× slowdown on AMD. **Why it matters:** If memory safety reaches GPU kernels through the compiler instead of `unsafe` raw pointers or vendor DSLs, it attacks one of the last bastions of `unsafe` in systems programming — with benchmarks that show the remaining gap rather than hiding it. [`🔗 arXiv:2608.13759`](https://arxiv.org/abs/2608.13759) · [`🔗 Byteiota analysis`](https://byteiota.com/rust-gpu-offload-hits-rustc-safe-portable-kernels-now/) --- ## 19. career-ops — the 64.9k-star "reverse-selection" job-search command center for AI coding CLIs - **Velocity:** ▮▮▮ trending - **Source:** GitHub · +218 stars today · ~12h ago (~12:03 UTC+8) - **Tags:** `ai-tools` `job-search` `agents` `cli` `open-source` **santifer/career-ops** (64.9k stars) turns any AI coding CLI (Claude Code, Codex, Gemini, Qwen…) into a job-search command center: it scans Greenhouse/Ashby/Lever portals, scores listings with a 10-dimension A–F rubric into a 1.0–5.0 score, flags scam/"ghost" postings, generates ATS-tailored PDF CVs, and tracks applications locally — human-in-the-loop, never auto-submits. The author used it to evaluate 740+ listings and land a Head of Applied AI role; WIRED and Business Insider have covered it. **Why it matters:** It inverts the "AI screens candidates" dynamic — candidates now run AI to reverse-select employers — and it's a model-agnostic, local-first example of agents applied to a non-coding domain. [`🔗 santifer/career-ops`](https://github.com/santifer/career-ops) · [`🔗 Tencent Cloud (中文)`](https://cloud.tencent.cn/developer/article/2696242) --- ## 20. Speko (YC S26) — an "OpenRouter for voice AI" that benchmarks and routes STT/LLM/TTS stacks - **Velocity:** ▮▮ rising - **Source:** Hacker News · 99 pts · ~1d ago (~12:03 UTC+8) - **Tags:** `voice-ai` `routing` `benchmark` `agents` `open-source` Speko's Launch HN ("OpenRouter for Voice AI") introduces a router for production voice agents: send criteria (accuracy/latency/cost, language, region), and it benchmarks 50+ providers / 140+ models across the STT, LLM, and TTS layers, picks the winner, and returns provider + model + scores in response headers. Its MIT-licensed gateway (**SpekoAI/gateway**, Go) runs as a local sidecar with BYOK and no call-home; hosted routing costs 5% over provider rates. Public boards publish WER, latency, and cost-per-minute at benchmarks.speko.ai. **Why it matters:** Voice stacks go stale because nobody re-benchmarks after launch; independent, continuously-updated evals plus a drop-in gateway turn "which STT/TTS for Spanish medical calls" into an answered, routeable question. [`🔗 speko.ai`](https://speko.ai) · [`🔗 SpekoAI/gateway`](https://github.com/SpekoAI/gateway) --- ## 21. NautilusTrader v2 — a Rust-native, nanosecond event-driven trading engine heads to 2.0 - **Velocity:** ▮ steady - **Source:** GitHub · 26k stars · ~12h ago (~12:03 UTC+8) - **Tags:** `trading` `rust` `backtesting` `open-source` `fintech` **nautechsystems/nautilus_trader** (26.1k stars) is a Rust-native, Python-strategy engine for multi-asset, multi-venue trading with a deterministic event-driven core shared between backtest and live (research-to-live parity). It's in its v2 release-candidate line (`2.0.0rc` wheels) with ~18 venue adapters (Binance, Interactive Brokers, Deribit, Polymarket, Betfair…), nanosecond-resolution simulation, and Redis-backed state persistence. **Why it matters:** Rust is absorbing the "performance + correctness" niche in trading infrastructure, and a stable 2.x API for a production-grade open engine lowers the barrier from hobby backtesting to real deployment. [`🔗 nautechsystems/nautilus_trader`](https://github.com/nautechsystems/nautilus_trader) · [`🔗 nautilustrader.io`](https://nautilustrader.io/) --- ## 22. Motrix 2.0.0-beta — the download manager returns after 3 years with an AI-agent-controllable CLI - **Velocity:** ▮ steady - **Source:** GitHub · +344 stars today · ~12h ago (~12:03 UTC+8) - **Tags:** `download-manager` `cli` `ai-agents` `open-source` `electron` **agalwood/Motrix** (53.2k stars) broke a three-year silence with **Motrix 2.0.0-beta** ("Motrix Turbo"), a full rewrite (Electron 43, React 19, TypeScript) adding a unified HTTP/FTP/BitTorrent download core shared with a new server/NAS mode, Docker deployment, and a `@motrix/cli` npm CLI that lets users — and **AI agents** — add/pause/resume downloads via natural-language commands. **Why it matters:** A dormant, widely-installed tool resurfacing with an explicit "AI Agent control" CLI is a clean example of agent-friendly surface area being added to a mature desktop app. [`🔗 agalwood/Motrix`](https://github.com/agalwood/Motrix) · [`🔗 Appinn (中文)`](https://meta.appinn.net/t/topic/90130) --- ## 23. Cursor launches Origin — a git forge "built for agent scale," days after GitHub's 7-hour outage - **Velocity:** ▮▮▮ trending - **Source:** Cursor Changelog · early beta · ~1d ago (~20:03 UTC+8) - **Tags:** `cursor` `code-hosting` `git` `agents` `developer-tools` Cursor shipped **Origin**, a cloud code-hosting service positioned as "a git forge built for agent scale," rolling out in early beta to all paid plans on Aug 17 — the same day GitHub suffered a ~7-hour outage affecting PRs, Issues, Actions, and Copilot. Origin lives in a new "Codebase" tab: repos at `cursor.com/codebase/{owner}/{repo}`, bidirectional real-time GitHub sync (GitHub stays the source of truth until you "Detach from GitHub"), full PRs with two-way comment/reaction sync, and launch integrations with Vercel (preview deploys), Depot, and Buildkite. It's built on Graphite's stacked-PR + merge-queue tech (Cursor acquired Graphite in Dec 2025), and Cursor reports **35% of its own internal PRs are already opened by autonomous agents** in cloud VMs. **Why it matters:** The first credible AI-native code host from a major coding-agent vendor — and the "agent scale" framing is backed by real telemetry, not marketing: human-oriented review workflows are the bottleneck AI-generated code now hits. > Agent-native features (asking the editor about a repo, cloud agents opening PRs against Origin remotes) are still rolling out; free plans and enterprise opt-out are gated. [`🔗 Cursor changelog`](https://cursor.com/changelog/origin-code-hosting) · [`🔗 SiliconAngle`](https://siliconangle.com/2026/08/17/cursor-launches-origin-code-hosting-service-to-compete-with-github/) --- ## 24. GitLab CVE-2026-19478 — unauthenticated GraphQL directive can modify or delete public projects (CVSS 9.4) - **Velocity:** ▮▮▮ trending - **Source:** GitLab · CVSS 9.4 · ~1d ago (~20:03 UTC+8) - **Tags:** `cve` `gitlab` `graphql` `code-injection` `self-hosted` GitLab released out-of-band critical patches (**19.2.4, 19.1.6, 19.0.8, 18.11.11**) on Aug 17 for **CVE-2026-19478** (CVSS 9.4, CWE-94): improper validation of a GraphQL directive lets an **unauthenticated** attacker modify or delete public projects and user data, with no user interaction. Reported by "hiimguardian" via HackerOne. There's no public PoC or confirmed in-the-wild exploitation yet, but full technical details drop ~90 days after the patch; the **18.2–18.10 branches have no fix**, so those installs must upgrade branches entirely. The same release patches CVE-2026-19650 (CSRF in GraphQL multiplex queries, CVSS 7.1). **Why it matters:** Self-managed GitLab is the on-prem default for orgs that won't host source in the cloud — an unauthenticated data-integrity flaw in the GraphQL layer is the worst case for a forge whose whole value is "your code, your server." [`🔗 GitLab patch release`](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-4-released/) · [`🔗 IONIX threat center`](https://www.ionix.io/threat-center/cve-2026-19478/) --- ## 25. iMonnit Express 4.0.5.5 — pre-auth SYSTEM RCE via an empty security-answer list and an eager plugin loader - **Velocity:** ▮▮ rising - **Source:** Full Disclosure (0day Rubbish) · CVSS 9.8 · ~12h ago (~20:03 UTC+8) - **Tags:** `cve` `imonnit` `rce` `auth-bypass` `iot` The **0day Rubbish Research Team** publicly disclosed a pre-authentication **SYSTEM RCE** (CVSS 9.8, no CVE assigned yet) in **iMonnit Express 4.0.5.5**, Monnit's Windows-based IoT sensor-monitoring gateway. The ASP.NET Core service runs as LocalSystem with no global `[Authorize]` filter, and three flaws chain together: an **empty security-answer list mints a valid admin cookie** → a **path-traversal file write** in the certificate-upload endpoint → a **plugin loader that calls `Assembly.Load` + `Activator.CreateInstance` before the `IExpressPlugin` check**, so the constructor executes as `NT AUTHORITY\SYSTEM`. The team verified `whoami = nt authority\system` and published the PoC on GitHub. **Why it matters:** Monnit gateways sit on industrial/environmental sensor fleets; a no-auth, no-interaction full chain with public PoC turns a monitoring appliance into a Windows domain pivot before a CVE even exists. [`🔗 Full Disclosure advisory`](https://seclists.org/fulldisclosure/2026/Aug/54) · [`🔗 0day Rubbish blog`](https://0day-rubbish.com/blog/imonnit-express-unauth-plugin-rce) --- ## 26. GPT-5.6 Sol goes 50% off on OpenRouter and Vercel — a channel-level price cut, not an OpenAI cut - **Velocity:** ▮▮▮ trending - **Source:** Vercel Changelog · 499 pts (HN) · ~8h ago (~20:03 UTC+8) - **Tags:** `openai` `pricing` `gpt-5-6-sol` `openrouter` `vercel` GPT-5.6 Sol's effective price halved on the two biggest routing platforms: **OpenRouter** (announced Aug 17, no end date) and **Vercel AI Gateway** (one month, through Sep 18, standard + Fast modes) both cut the flagship to **$2.50/M input and $15/M output** (cache read $0.25). OpenAI's own API price is unchanged at $5/$30 — the discount lives at the aggregator, and SemiAnalysis floated that the platforms' public token-usage reporting is exactly why a temporary discount could lift Sol's measured share. It follows the July 30 cut on the cheaper Luna/Terra tiers. **Why it matters:** The most capable model in the GPT-5.6 family at half price meaningfully shifts agent token economics — while quietly showing how much of "frontier pricing" is now set by routing platforms, not the lab. [`🔗 Vercel changelog`](https://vercel.com/changelog/gpt-5-6-sol-is-50-off-on-ai-gateway-for-the-next-month) · [`🔗 OpenRouter pricing`](https://openrouter.ai/openai/gpt-5.6-sol) --- ## 27. OpenViking — Volcengine's self-evolving context database treats agent memory as a `viking://` filesystem - **Velocity:** ▮▮ rising - **Source:** GitHub · 29k stars · ~12h ago (~20:03 UTC+8) - **Tags:** `agent-memory` `context-database` `rag` `volcengine` `open-source` **volcengine/OpenViking** (AGPL-3.0, ~29k stars) unifies agent memory, knowledge RAG, and skills behind a virtual filesystem: content gets a `viking://` URI and agents browse it with `ls`/`tree`/`find` instead of opaque vector queries. Everything is auto-tiered **L0/L1/L2** (abstract → overview → full details) to cut token spend, retrieval is directory-recursive with an observable trajectory, and `session.commit()` asynchronously mines user preferences + agent experience into durable long-term memory. On the LoCoMo benchmark it lifts agent memory accuracy from 24–57% native to **80–83%** while cutting input tokens 34–91% and latency 58–66%. **Why it matters:** It attacks "context fragmentation" and token waste by making an agent's entire context base inspectable and self-improving — a filesystem for memory rather than a black-box vector store, from ByteDance's cloud arm. [`🔗 volcengine/OpenViking`](https://github.com/volcengine/OpenViking) · [`🔗 OpenViking docs`](https://docs.openviking.ai/en/faq/faq) --- ## 28. Kozuchi Agent — a language-agnostic open-weight repair agent hits 374/500 SWE-bench Verified on Qwen3.5-27B - **Velocity:** ▮▮ rising - **Source:** arXiv · ASE '26 · ~12h ago (~20:03 UTC+8) - **Tags:** `research` `software-repair` `swe-bench` `open-weight` `agent` **Kozuchi Agent** (arXiv:2608.15579, accepted at ASE '26 Industry Showcase) is a language-agnostic, open-weight software-repair agent built on a locally hosted **Qwen3.5-27B with no fine-tuning** — explicit phases, persistent state, deterministic tools, and cross-agent test-time selection keep every run auditable. It resolves **374/500 SWE-bench Verified** on the official evaluator (TTS@8), ranks **first among open-weight systems** on Multi-SWE-bench Java (32.03%, 4th of 42 overall) and 12th of 135 on Python, with per-phase behavior stable within ±5pp across languages. **Why it matters:** A deterministic pipeline around a mid-size open model that approaches frontier repair results — a reproducibility-first counterpoint to black-box frontier agents, and evidence that harness engineering, not model scale, is the lever. [`🔗 arXiv:2608.15579`](https://arxiv.org/abs/2608.15579) · [`🔗 SciRate`](https://scirate.com/arxiv/2608.15579) --- ## 29. ai-agent-book — 李博杰 open-sources a 38.9k-star, 10-chapter AI-agent engineering textbook with 103 runnable experiments - **Velocity:** ▮▮ rising - **Source:** GitHub · 38.9k stars · ~12h ago (~20:03 UTC+8) - **Tags:** `ai-agents` `book` `open-source` `chinese` `education` **bojieli/ai-agent-book** (Apache-2.0) is 李博杰 (Bojie Li)'s fully open textbook 《深入理解 AI Agent》(Understanding AI Agents), organized around the formula **Agent = LLM + Context + Tools**: full text, figures, and **103 runnable companion experiments** across 10 chapters — context engineering, memory/RAG, tools & MCP, coding agents, evaluation, post-training, self-evolution, and multi-agent collaboration — plus community translations in 13 languages and compiled PDF/EPUB builds. Li (ex-Huawei "Genius Youth", now Pine AI chief scientist) coined "Harness engineering": everything outside the model is where the real competitive edge is. **Why it matters:** A production-grade agent curriculum with executable experiments, free and open — the rare practitioner-authored path from principles to multi-agent systems, now the most-starred agent-education repo. [`🔗 bojieli/ai-agent-book`](https://github.com/bojieli/ai-agent-book) · [`🔗 CSDN (中文)`](https://blog.csdn.net/aiwording/article/details/163452714) --- ## 30. AERIS-10 — an open 10.5 GHz phased-array radar, 24k stars, with independent analysis disputing its range claims - **Velocity:** ▮ steady - **Source:** GitHub · 24.2k stars · ~12h ago (~20:03 UTC+8) - **Tags:** `hardware` `radar` `fpga` `sdr` `open-source` **NawfalMotii79/PLFM_RADAR** ("AERIS-10") is a fully open, low-cost **10.5 GHz pulse-LFM phased-array radar**: ±45° electronic beam steering + 360° mechanical scan, 16× GaN PA channels, an **XC7A50T FPGA** handling pulse compression/Doppler FFT/MTI/CFAR, and an STM32 controller — in 3 km (Nexus) and 20 km (Extended) variants. Hardware is CERN-OHL-P, firmware/software MIT, and it's been **accepted by Crowd Supply** for a Q3 2026 campaign. Independent analysis (KolesnykMaksym/plfm-radar-analysis) flags caveats: the headline ranges may be **overstated 7–13×** for realistic 1 m² targets (~0.4 km / ~1.6 km), and the README's XC7A100T doesn't match the XC7A50T in the schematics. **Why it matters:** Radar has been a closed, defense-gated domain; an open BOM + FPGA + firmware design democratizes it for SDR/robotics/drone research — while the honest independent teardown is exactly the scrutiny an ambitious hardware claim needs. [`🔗 NawfalMotii79/PLFM_RADAR`](https://github.com/NawfalMotii79/PLFM_RADAR) · [`🔗 Hackaday.io project`](https://hackaday.io/project/205190-open-source-plfm-radar-up-to-20km-range) --- ## 31. τ0-VLA — a hierarchical robot foundation model that spends test-time compute where decisions are hard - **Velocity:** ▮ steady - **Source:** arXiv · 39 authors · ~12h ago (~20:03 UTC+8) - **Tags:** `robotics` `vla` `foundation-model` `world-model` `arxiv` **τ0-VLA** (arXiv:2608.16885) is a hierarchical vision-language-action robot foundation model: a **high-level policy** generates subtasks using **world-model-guided test-time computation** — searching alternative subtask choices before committing, allocating more compute to difficult or high-stakes decisions — while a **low-level policy** executes each subtask across embodiments. Trained on **40,115 hours of heterogeneous real-world data** with multimodal co-training, it shows that extra test-time compute substantially improves next-subtask accuracy in-domain and distribution-shifted, translating to higher closed-loop success on long-horizon manipulation. **Why it matters:** It extends the "test-time compute scales capability" finding from language models to robot control — compute spent where a plan is uncertain, not uniformly across a task. [`🔗 arXiv:2608.16885`](https://arxiv.org/abs/2608.16885) · [`🔗 SciRate`](https://scirate.com/arxiv/2608.16885) --- ## 32. munder-difflin — a local multi-agent harness that runs "an office of your clones" from real terminal CLIs - **Velocity:** ▮ steady - **Source:** GitHub · 1.7k stars · ~12h ago (~20:03 UTC+8) - **Tags:** `multi-agent` `local-first` `electron` `claude-code` `open-source` **chaitanyagiri/munder-difflin** (MIT) is a local-first multi-agent harness that wraps real terminal CLIs — Claude Code, Codex, Gemini CLI, Qwen, Kimi, OpenCode, Copilot — as agents in `node-pty` pseudo-terminals, then coordinates them on a Pixi.js "office floor." A **GOD orchestrator** routes tasks and escalates only spend/scope/destructive decisions; agents share a git-backed "hive" (memory, mailboxes, blackboard) with semantic recall, per-agent worktrees, token/cost telemetry, a steer→constrain→stop circuit breaker, and human-in-the-loop gates. **Why it matters:** A polished, TypeScript-native answer to running a self-managing team of coding agents on your own machine — with the safety rails (spend/scope/destructive gates) that cloud orchestrators tend to leave to the user. [`🔗 chaitanyagiri/munder-difflin`](https://github.com/chaitanyagiri/munder-difflin) · [`🔗 Peerlist`](https://peerlist.io/chaitanyagiri/project/munder-difflin-free-local-multiagent-harness) --- ## Metadata | Field | Value | |-------|-------| | Generated | 2026-08-18T20:03:00Z | | Items | 32 | | Sources tracked | 40 (GitHub, Hacker News, Wiz, The Register, DuckDB, CISA, Suriq, IONIX, CVE.org, Tencent Cloud, OffSeq, Mintlify, agentskills.io, ITHome, The Block Beats, RuntimeWire, Leiphone, arXiv, SciRate, Rickmanelius, Wordfence, The Hacker News, Criminal IP, Gitea Blog, Roboflow, Byteiota, Speko, NautilusTrader, Appinn, Cursor, SiliconAngle, GitLab, Full Disclosure, 0day Rubbish, Vercel, OpenRouter, OpenViking Docs, CSDN, Hackaday.io, Peerlist) | | Update schedule | 04:03, 12:03, 20:03 UTC+8 (3x daily) | | Ranking | Velocity-weighted (recency × engagement acceleration × source authority) | | License | [CC-BY 4.0](https://creativecommons.org/licenses/by/4.0/) | --- [Previous day](../2026-08-17/) · [Raw .md](../2026-08-18.md) · [Archive](../../archive/)