Topics
Browse posts by category and tag — every topic we cover, with the latest pieces under each.
Tags
- #vulnerability-management 9
- #ml-cve 8
- #ml-supply-chain 7
- #model-security 6
- #deserialization 5
- #supply-chain 5
- #cve 4
- #ml-security 4
- #ai-infrastructure 3
- #pickle 3
- #ai-supply-chain 2
- #keras 2
- #langchain 2
- #pytorch 2
- #safetensors 2
- #serialization 2
- #tensorflow 2
- #transformers 2
- #agent-security 1
- #ai-bom 1
- #ai-security 1
- #code-injection 1
- #cve-tracking 1
- #cyclonedx 1
- #devsecops 1
- #exploitation 1
- #gguf 1
- #hugging-face 1
- #inference 1
- #kev 1
- #litellm 1
- #llama-cpp 1
- #llm-security 1
- #machine-learning 1
- #machine-learning-security 1
- #mlflow 1
- #mlops 1
- #mlsec 1
- #mlsecops 1
- #nvd 1
- #ollama 1
- #onnx 1
- #owasp 1
- #path-traversal 1
- #picklescan 1
- #prompt-injection 1
- #ray 1
- #sbom 1
- #spdx 1
- #triage 1
- #triton 1
- #vllm 1
- #vulnerability-scanning 1
Categories
Vulnerability Tracking 8 posts
- AI CVEs in CISA KEV: Ray, LiteLLM, and What's MissingThree AI-stack CVEs sit in the CISA KEV catalog: one Ray, two LiteLLM. What confirmed exploitation looks like, and why ShadowRay still is not listed.
- Inference Server CVEs: vLLM, Ollama, llama.cpp, TritonThe serving layer now outproduces model files for critical CVEs. Verified entries in vLLM, Ollama, llama.cpp and Triton, and the three defects behind them.
- MLflow CVEs: Why 2.14.1 Still Fails Your ScannerMLflow carries 80 published advisories and 17 with no patched version. Why scanning 2.14.1 returns unfixable findings, and which ones need real action.
- Model File Format Security: Pickle, Safetensors, GGUFWhich model formats can execute code when loaded, which only crash, and which are inert. A format-by-format comparison built from the verified CVE record.
- PyTorch Security: Notable CVEs and Hardening the Loading PathPyTorch's most consequential CVEs cluster on one thing: loading a model file that runs code. A walk through the verified entries and how to harden.
- trust_remote_code and the ML Orchestration CVE ClassA second family of ML supply-chain CVEs has nothing to do with weights and everything to do with the glue: trust_remote_code and orchestration servers.
defense 2 posts
- How to Triage an ML-Stack CVE: A Practical WorkflowA repeatable workflow for taking an ML-library CVE from 'a scanner flagged it' to a defensible decision, without panic-patching or trusting the score.
- Reading an ML Library CVE: What to Extract Beyond the CVSS ScoreML library CVEs are usually scored against a generic threat model that doesn't match how the library is used in production AI systems.
ML Security 2 posts
- Malicious Model File Detection: Auditing ML ModelsPickle serialization flaws, PickleScan bypass CVEs, and a practical detection stack for teams pulling models from public repositories like Hugging Face.
- TensorFlow Security Vulnerabilities 2026: CVEs and Supply ChainA breakdown of the top TensorFlow security vulnerabilities in 2026: CVE-2025-49655, CVE-2025-12058, DoS flaws in 2.18.0, and supply chain risk.