Skip to content
EventPast event

Decepticon agent ChatML role boundary injection vulnerability

1 reports1 reporting sources

Start here

AI overview

Versions before autonomous red team agent Decepticon 1.1.17 have a ChatML role boundary injection vulnerability CVE-2026-61732 with a CVSS score of 10.0; 1.1.17 has fixed it. The agent directly wraps web crawl results targeting the target service into LLM messages without neutralizing the literal ChatML special tokens in them; in BYOK deployment mode, users can configure any OpenAI-compatible endpoint, and inference backends such as vLLM, SGLang, Ollama, and LM Studio parse these special tokens, so crawled content can inject role boundaries and hijack agent behavior.

Generated by AI from reports · Updated 5 days ago

Progress timeline

Date not provided
  1. Date not given
    DevGuard Vulnerability DatabaseSelected
    Decepticon red team agent exposed to ChatML role boundary injection vulnerability CVE-2026-61732, fixed in 1.1.17

    Versions before autonomous red team agent Decepticon 1.1.17 have a ChatML role boundary injection vulnerability CVE-2026-61732 with a CVSS score of 10.0; 1.1.17 has fixed it. The agent directly wraps web crawl results targeting the target service into LLM messages without neutralizing the literal ChatML special tokens in them; in BYOK deployment mode, users can configure any OpenAI-compatible endpoint, and most open-source and self-hosted model providers such as vLLM, SGLang, Ollama, LM Studio, and text-generation-webui do not filter special token literals in user content by default. These literals are parsed as structural role boundary token IDs, so strings planted by an attacker in a target webpage can forge new operator turns that the model treats as authoritative, bypass Decepticon's agent guardrails, and achieve arbitrary command execution in the Kali Linux sandbox.

Related discussion

No discussion links have been collected for this event yet.

Attention trend

New sources per day

1 in 10 days·most 1 (Oct 5)·today 0

  • Oct 5: 1 new sources (1 outlets, 0 accounts)
  • Oct 6: 0 new sources (0 outlets, 0 accounts)
  • Oct 7: 0 new sources (0 outlets, 0 accounts)
  • Oct 8: 0 new sources (0 outlets, 0 accounts)
  • Oct 9: 0 new sources (0 outlets, 0 accounts)
  • Oct 10: 0 new sources (0 outlets, 0 accounts)
  • Oct 11: 0 new sources (0 outlets, 0 accounts)
  • Oct 12: 0 new sources (0 outlets, 0 accounts)
  • Oct 13: 0 new sources (0 outlets, 0 accounts)
  • Oct 14: 0 new sources (0 outlets, 0 accounts)

Hourly attention

No comparable trend data