Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61732 critical CVSS 10.0

Vulnerability in decepticon-core (CVE-2026-61732)

Summary

Vulnerability in decepticon-core (CVE-2026-61732). Successful exploitation can lead to full system takeover. Exploitable via nmap. Mitigation: upgrade to 1.1.17 or later.

Original description

The description as published by the source.

Summary

Decepticon wraps web crawl results — the output of agent reconnaissance against target services — into LLM messages without neutralizing ChatML special-token literals. Under the BYOK (Bring Your Own Key) deployment model, users configure their own LLM credentials to any OpenAI-compatible endpoint. Most open-source and self-deployed model providers (vLLM, SGLang, Ollama, LM Studio, text-generation-webui, etc.) do not filter special-token literals from user content in their default configurations. Those literals are parsed into structural role-boundary token IDs, meaning an attacker string planted in a target web page forges a new operator turn the model treats as authoritative, bypassing Decepticon's agent guardrails and resulting in arbitrary command execution inside the Kali Linux sandbox.

The vast majority of open-source and self-deployed model providers do not filter special-token literals. vLLM explicitly declined to fix this issue on 2026-04-21, closing it as "out of scope for the inference layer." Fix responsibility therefore falls squarely on the Agent application layer. OpenClaw completed an analogous fix on 2026-04-22 via commit 2514746b3261 (~30 lines, sanitizer applied just before tool-output wrapping), demonstrating the feasibility of application-layer mitigation.

Applicability

Confirmed vulnerable when Decepticon is configured with a BYOK OpenAI-compatible backend whose tokenizer preserves special-token IDs — vLLM / SGLang / TGI confirmed upst…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61732 has been found in decepticon-core.
Attackers can target a specific entry point like nmap over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade decepticon-core to 1.1.17 or later.
If unsure, ask your IT team or search "decepticon-core CVE-2026-61732" on the vendor's site.

CVE-2026-61732 (decepticon-core) — CWE-74 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: nmap / httpx / dnsx / masscan
Patched: 1.1.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-74) exists in decepticon-core. Attackers reach the vulnerable code path via nmap without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of decepticon-core. Attack surface: nmap / httpx / dnsx / masscan.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.1.17.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decepticon-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'decepticon-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で decepticon-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade decepticon-core to 1.1.17

    ステージング環境で 1.1.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip decepticon-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.17"}]}]
pip decepticon
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.17"}]}]
pip decepticon-sdk
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.17"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details