Cue — agentic threat model
Cue is a coding agent designed to accelerate software development, presenting high agentic risk due to its potential access to code repositories, execution environments, and developer credentials, which could be leveraged for supply chain attacks or remote code execution if compromised.
OWASP AIVSS score rationale
| Autonomy of Action | 0.70 | |
| Goal-Driven Planning | 0.80 | |
| Self-Modification | 0.20 | |
| Dynamic Tool Use | 0.80 | |
| Persistent Memory | 0.60 | |
| Contextual Awareness | 0.70 | |
| Dynamic Identity | 0.40 | |
| Multi-Agent Interactions | 0.20 | |
| Non-Determinism | 0.70 | |
| Opacity & Reflexivity | 0.50 |
Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.
MAESTRO 7-layer threat model
Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.
Not certain from the listing — likely relies on commercial LLMs optimized for code generation. Threats include prompt injection leading to the generation of insecure or malicious code, and model reprogramming.
Not certain from the listing — likely ingests local codebase files, repository history, and developer documentation. Threats include codebase poisoning where malicious code in the repository influences the agent's outputs.
Not certain from the listing — likely uses an orchestration framework to plan, write, and test code. Threats include insecure tool integration, such as executing arbitrary shell commands during testing or compilation.
Not certain from the listing — requires sandboxed execution environments to run and test generated code safely. Threats include container escape or host compromise if code execution is not properly isolated.
Not certain from the listing — requires monitoring of generated code quality and execution logs. Threats include blind spots in detecting malicious code patterns or backdoor insertions.
Not certain from the listing — requires strict access controls (RBAC) for repository write permissions and secrets management. Threats include unauthorized code commits or credential theft.
Not certain from the listing — may interact with package managers, CI/CD pipelines, or external APIs. Threats include supply chain attacks through compromised third-party dependencies.
MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).