ZeroHour
Product

vLLM

2 mentions in 7 days · 7 in 30 days · 7 total · first seen · last

Timeline

The AI Supply Chain Has a Security Problem, and Much of It Is Sitting on the Open Internet

Researchers counted 36,769 publicly reachable self-hosted AI endpoints, only about 2% behind HTTP authentication, exposing Ollama, vLLM, and Flowise to abuse.

A Mysterium VPN study found 36,769 self-hosted AI endpoints reachable through internet scanning, with only 2.02% returning an HTTP authentication challenge. Open WebUI accounted for 18,529 reachable instances, Ollama for 6,935 fingerprinted hosts, and 5,223 agent-builder and workflow platforms were exposed, often holding API keys, database credentials, and other secrets. The report highlights LLMjacking risk from exposed Ollama APIs, a critical Flowise bug (CVE-2026-40933), leaked n8n tokens, and prior SentinelOne/Censys research finding roughly 175,000 exposed Ollama hosts in 130 countries.

DeepSeek AI Released DeepSeek-V4.1-Flash with 1M Context, FP4 KV Cache, and Cross-Layer Attention Reuse

DeepSeek released open-weight V4.1-Flash, a 552B MoE model with 1M context and FP4 KV cache, beating Opus-5 and GPT-5.6 Sol on agent benchmarks.

DeepSeek-V4.1-Flash is a multimodal Mixture-of-Experts model with a 552B-parameter backbone plus 196B Engram parameters, activating 8B parameters at prefill and 16B at decode, with a 1M-token context window. It introduces a causal encoder-decoder design, Compressed Sparse Attention 2, and FP4 (E2M1) KV cache quantization, cutting global KV cache to 890 bytes per token, about 1/4 of V4-Flash and 437x smaller than V1. Pre-training covered 45T multimodal tokens; the MIT-licensed weights ship on Hugging Face with vLLM and SGLang support. It scores 90.6 on Terminal-Bench 2.1 and 74.2 on DeepSWE v1.1, ahead of Opus-5 and GPT-5.6 Sol.

MarkTechPost · 5d agoModel release1

AI-Infra-Guard: Open-source security scanner for AI systems

Tencent's Zhuque Lab open-sourced AI-Infra-Guard, a scanner that fingerprints AI services, checks 1,600+ CVEs, and evaluates MCP skills.

AI-Infra-Guard fingerprints running AI services such as Ollama, vLLM and ComfyUI, checks them against more than 1,600 known CVEs, and inspects MCP servers and agent skills across 14 risk categories. Its SkillTrustBench judging set contains 5,520 human-labeled samples, with false positive rates of 1.20%–18.67% depending on the judging model. Users include ICBC, China Merchants Bank, China Telecom, Lenovo, vivo and Bilibili. Release 4.1.9 hardened scanning agents against indirect prompt injection, and the open-source build ships without authentication, requiring a reverse proxy with Basic Auth or an IP allowlist.

Help Net Security · 7d agoTools

Speculative Decoding in vLLM on AMD GPUs

vLLM benchmarks speculative decoding on AMD Instinct MI300X and MI355X GPUs across five drafting methods including EAGLE-3 and native MTP.

The vLLM project documents draft-and-verify speculative decoding support for AMD GPUs via ROCm, comparing native MTP, Gemma 4 MTP, EAGLE-3, DFlash, and DSpark drafting approaches. Output-token throughput effects varied with drafting method, proposal length, model family, draft checkpoint, workload, and acceptance behavior. The post also covers how to enable each method plus practical tuning and observability considerations.

Perplexity Details Its GPU Embedding Stack: How Ivy, Tulip and ROSE Serve pplx-embed

Perplexity details its GPU embedding serving stack (Ivy, Tulip, ROSE), which reuses LLM prefill/decode kernels, CUDA graphs, and LazyTensors to cut launch overhead.

Perplexity engineers published a deep dive on the serving infrastructure behind pplx-embed, used across Perplexity Search and its API platform. The stack comprises Ivy (Rust HTTP gateway), Tulip (gRPC scheduling and batching), and ROSE (Runtime-Optimized Serving Engine), which reuses LLM prefill and decode kernels rather than running a separate embedding engine. Optimizations include whole-model CUDA graphs with lazy capture and a LazyTensor abstraction that overlaps CPU batch preparation with in-flight GPU work. Benchmarks are reported against vLLM v0.22.0 in BF16, with FlashAttention 4 generally fastest but FlashInfer 3 winning on Qwen-based models at very long sequence lengths.

MarkTechPost · 10d agoAI tools & infra

nvidia/Qwen3.8-Flash-Next-NVFP4 — new model trending #28 on Hugging Face

NVIDIA released an NVFP4 4-bit quantized build of Alibaba's Qwen3.8-Flash-Next, a 125B-parameter MoE vision-language model, via Model Optimizer.

The checkpoint quantizes Qwen3.8-Flash-Next — a hybrid-attention (Gated DeltaNet and Qwen Sparse Attention) Mixture-of-Experts model with 125B total and 6B activated parameters, plus 51B n-gram embeddings and 4B MTP — using NVIDIA Model Optimizer v0.46.0. NVFP4 benchmarks stay close to FP8: GPQA Diamond 91.5 vs 92.0, MMMU Pro 78.3 vs 77.1, Terminal-Bench 2.1 82.9 vs 83.3. It targets Blackwell B200/B300 GPUs, runs on vLLM, supports 262K context extendable to 1M tokens, and is licensed under the NVIDIA Open Model License with Qwen Community License 1.0.

Hugging Face trending models · 14d agoModel release

dealignai/GLM-5.3-CYBERSECURITY-FP8 — new model trending #13 on Hugging Face

dealignai releases GLM-5.3-CYBERSECURITY-FP8, a 753B MoE weight-modified variant cutting refusals on offensive-security prompts, trending #13.

dealignai released GLM-5.3-CYBERSECURITY-FP8 on Hugging Face, a cybersecurity-domain 'crack' of the 753B-parameter GLM-5.3 MoE model, currently trending #13. The release directly edits bf16 residual writers, keeps FP8 routed experts, and serves with stock vLLM on 8x H200 GPUs with 131k context. HarmBench-320 evaluations show 80-84% direct harm compliance and 89% cyber-offense compliance, while MMLU rose 1.07 points to 86.65%. Copyright-verbatim reproduction remains a known soft-refusal limitation, with an UNCENSORED sibling variant offered.

Hugging Face trending models · 16d agoModel release

Related CVEs

  • Flowise is a drag & drop user interface to build a customized large language model flow.
    Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, due to unsafe serialization of stdio commands in the MCP adapter, an authenticated attacker can add an MCP stdio server with an arbitrary command, achieving command execution. The vulnerability lies in a bug in the input sanitization from the “Custom MCP” configuration in http://localhost:3000/canvas - where any user can add a new MCP, when doing so - adding a new MCP using stdio, the user can add any command, even though your code have input sanitization checks such as…
    · flowiseai flowise PoC

Appears with

Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.