The library combines 88 AIDEFEND in Action analyses, 69
AIDEFEND SecureFlow attack flows, and 44 evidence-checked primary-report records.
Of these, 156 have
evidence-bounded AITBM scenarios with uncertainty intervals, while 45 retain
traceable attack steps and AIDEFEND mappings without an ERS (0 awaiting analysis,
45 not scorable by design).
These are not assessments of record. Search by incident, architecture, AITBM sub-metric, or
AIDEFEND technique, or browse the categories below.
156calculated use casesout of 201 source records
4.8median indicative ERS
4Critical MVT confirmed
88Compound Risk Alerts
Indicative ERS midpoints span 3.1–8.0:
23 High, 45 Moderate, and 88 Low-Moderate.
Unknown controls remain unknown; no case is forced to Critical because evidence is absent.
INCIDENT REFERENCE COLLECTIONS
Browse the library by threat and system type
Use focused collections to find comparable incidents,
reusable evaluation questions, related AITBM sub-metrics, and framework routes.
SCORING METHODHow these scores were produced
Read the assumptions, uncertainty rules, and evidence limits behind every case.
Each scored case is a retrospective public-evidence scenario for a bounded affected configuration,
built from the cited vendor, maintainer, researcher, or
AIDEFEND in Action
analysis. Attack-flow records mirrored from
AIDEFEND SecureFlow
carry ordered attack steps and step-matched defenses but no score. It is a website companion, not an AITBM assessment
of record and not a statement about any vendor's current product.
Unknown is not NOT APPLICABLE
Architecture alone determines applicability. Missing public
evidence remains unknown. The result is recomputed with unknown applicable inputs at 1.00, 0.50,
and 0.00 to show the best-security bound, maximum-entropy midpoint, and worst-security bound.
Only observed controls earn credit
A demonstrated allowlist rejection, authorization denial, or
integrity verification can raise a sub-metric. A recommended defence, presumed log, or product
capability does not prove operation in the assessed configuration and earns no positive credit.
Cascade Potential is graph-derived, and usually defaults
Cp is not read off a prose ladder: it comes from a verified System
Dependency Graph, and spec 3.2.1 forces Cp = 1.00 whenever no such graph exists. No
organisation publishes one after an incident, so Cp sits at 1.00 throughout. Each case says whether
that was corroborated by an observed ungated path to a privileged node, or is merely the
worst-case default — 87 of 156 rest on the default alone.
Assurance is normalized for comparison
The comparative scenario fixes ACI at 1.00 so article completeness
does not overwhelm the system-risk signal. The public-evidence ACI is still calculated and shown as a
diagnostic, but it is not represented as actual system assurance or inserted into the scenario ERS.
How to read the midpoint and interval
The midpoint assigns every unknown applicable sub-metric 0.50, the expected value of a maximum-entropy
prior over the five rubric anchors. This is a deterministic comparison convention, not a finding that
an undisclosed control achieved 0.50. The interval is the primary uncertainty statement.
The midpoint supports transparent comparison between the case studies; it must always be quoted with
its interval and the label Indicative ERS (normalized-assurance
scenario). A first-party assessment replaces the interval with measured inputs and uses its
actual ACI in the normative ERS formula.
The interval is conditional on the single Operational Risk Posture the workpaper asserts. Optional cited
ORP ranges, admission decision records and non-ERS evidence profiles are described on the
evidence-scenario method page;
no current case uses them, and no existing score changes.
Temporal evidence is diagnostic, not normalized to seven days
Every workpaper preserves its documented evidence age and event caps. Those values calculate a
public-evidence ACI diagnostic on the stated reference date. The generator no longer overwrites every
case with a seven-day age, because a constant would be a scenario assumption rather than measured
evidence freshness.
The Behavioral Attestation Window uses the specification's non-double-counting rule:
lambdabehavior = lambdatier × Mthreat ×
max(MTDI, MEm). The public-evidence ACI does not determine the comparative
midpoint; it tells readers how much confidence the article package itself can support.
READ THIS BEFORE QUOTING A NUMBER
These are case-study scenarios, not vendor ratings. Each result
describes one documented configuration or representative boundary. Remediation and current products
are outside the score unless a separate reassessment is performed.
All 156 scenarios use the current 26-sub-metric basis as of
2026-10-18. Cn-7 remains UNKNOWN unless the public evidence establishes resource-budget
and execution-loop containment, and Ro-5, Cn-8, and Cn-9 remain UNKNOWN unless the evidence records an observed
artifact-admission, untrusted-context, or self-modification control outcome; UNKNOWN stays in the interval and is never converted into inferred credit.
Quote the midpoint with its interval. Public evidence cannot
establish all 26 current sub-metrics, a verified dependency graph, or an assessment-of-record ACI. The
midpoint is useful only with its best-to-worst unknown-input bounds and normalized-assurance label.
Judgement was applied, and it is shown. Rubric placement is an
assessor call. Every placement on this page carries the evidence behind it precisely so a reader can
disagree with a specific number instead of the whole result.
The arithmetic and unknown-input rule are fixed. Scores are computed by
the framework's own formulas, and the engine is checked against the Finbot worked example
(ERS = 10.0, CRM = 1.35, Critical MVT) on every build. If that anchor ever fails to
reproduce, this page refuses to build.
The verified failure is an alternate task-authority route and public token publication; secret-filter efficacy as a five-level metric remains unmeasured.
Controls that hold still score at the anchor they evidence: auto_login disabled and no public flow defeated an autonomous, AI-driven exploit, yet they prove only the basic Cn-5 and Cn-1 anchors, so the…
Tool-calling LLM
Published CVSSCVE-2026-33017 · CVSS 4.0 Base 9.3 Critical · GitHub_M
When an agent's control interface is internet-reachable without effective authentication, identity, scope, escalation and output filtering all fail through the same door, so every Containment sub-metric the…
A researcher-built replica on a real agent platform can be scored as a representative configuration when the source states its trigger, tools and reach — but its fidelity is staging-equivalent, and an…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.5range 3.3–10.0
MVT evidenceMVT indeterminate
2026-09-18 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
A production model was observed on exploited Ray infrastructure, permitting a narrowly bounded host-inheritance score for the unauthenticated Jobs path; no model tampering is evidenced.
Tool abuseModel pipeline
CVSS — no applicable published score verified
Indicative ERS4.8range 1.4–8.2
MVT evidenceMVT indeterminate
2026-09-15 · AIDEFEND in Action · Agentic / MCP System · Tier 3
OX reproduced a default DeepSeek Harness local control path: a confined coding agent called an unauthenticated loopback API, spoofed a trusted Host, changed its own session to danger-full-access, and…
Agentic / MCP
Published CVSSCVE-2026-82533 · CVSS 4.0 Base 9.4 Critical · OX SecurityCVE-2026-82533 · CVSS 3.1 Base 9.6 Critical · VulnCheck CNA
Indicative ERS4.1range 1.2–7.0
MVT evidenceMVT indeterminate
2026-09-15 · AIDEFEND in Action · Standalone LLM / Generative AI · Tier 2
Sysdig recorded 10 attacker requests in eight minutes against its LMDeploy VLM-serving honeypot. Requests supplied image_url values through chat completions to probe IMDS and loopback services; unrestricted…
Tool-calling LLM
Published CVSSCVE-2026-33626 · CVSS 3.1 Base 7.5 High · GitHub maintainer advisory
Check Point reproduced cross-account data relay through a shared JFrog Artifactory reachable from two otherwise isolated ChatGPT code containers. The attacker-controlled shared conversation induced victim…
Tool-calling LLM
CVSS — no applicable published score verified
Indicative ERS4.0range 1.1–6.9
MVT evidenceMVT indeterminate
2026-09-13 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Zenity demonstrated one Claude in Chrome prompt-injection boundary: an attacker-origin email instructed the browser agent to import code via javascript_tool in an authenticated browser session, then read…
Adversa demonstrated a Grok web-chat browsing path in which a hostile page induced runtime decryption of attacker instructions and privileged navigation to an attacker URL containing private session context…
Qwen Code processed packaged Git configuration during startup before agent authorization and ran a configured helper as the developer. The attack requires a delivered repository directory or ZIP with…
The first agent message caused Hermes Git context gathering to invoke an executable helper from packaged .git/config as the developer. The attack requires a delivered repository directory or ZIP with…
Agentic / MCP
Published CVSSCVE-2026-71963 · CVSS 4.0 Base 8.6 High · CVE CNACVE-2026-71963 · CVSS 3.1 Base 8.8 High · VulnCheck CNA
Grok Build processed the packaged Git configuration on the first keystroke and ran a configured helper as the developer. The attack requires a delivered repository directory or ZIP with .git/config files;…
Review of a ZIP-delivered repository with executable .git/config caused Goose Git context gathering to run a configured helper as the developer, outside the agent sandbox. The attack requires a delivered…
Agentic / MCP
Published CVSSCVE-2026-72718 · CVSS 4.0 Base 7.0 High · GitHub maintainer CNA
The ultrareview workflow triggered a second Git setting path from packaged .git/config and executed a helper as the developer; the exact setting key was not disclosed. The attack requires a delivered…
Claude Code startup Git context collection triggered core.fsmonitor from packaged .git/config, executing a command as the developer before an approval boundary. The attack requires a delivered repository…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS4.1range 1.2–7.0
MVT evidenceMVT indeterminate
2026-08-25 · AIDEFEND in Action · Agentic / MCP System · Tier 2
The memory branch demonstrates persistent-state containment failure, now covered by Cn-9. A webpage-derived record entered durable memory without a promotion gate, and Varonis found that password changes,…
Data exposureAgentic / MCP
Published CVSSCVE-2026-24301 · CVSS 3.1 Base 8.8 High · microsoft
Indicative ERS8.0range 3.9–10.0
MVT evidenceMVT floor: at least Major
2026-08-25 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Disabling web search did not remove the sink, and that is the scoring lesson: Cn-1 is not measured by which features are switched off but by the complete inventory of outbound-capable tools an untrusted…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.6range 3.0–10.0
MVT evidenceMVT indeterminate
2026-08-25 · AIDEFEND in Action · Agentic / MCP System · Tier 2
The blast radius came from the managed runtime boundary, not from the compromised Playbook. Tr-3 scores 0.00 rather than 0.25 because the decisive event produced no record at all and the Playbook could then…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS4.7range 2.4–7.0
MVT evidenceMVT floor: at least Major
2026-08-25 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Computer-use agents introduce a physical gap between perception and action, and AITBM prices it as a Containment failure rather than a perception failure. The screenshot was accurate when taken and the…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.3range 2.6–10.0
MVT evidenceMVT indeterminate
2026-08-25 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Cn-6 scores 0.00 for a reason the per-action view would miss: the write that overwrote cursorsandbox and the command that later ran unsandboxed are different hops, and neither is individually catastrophic.…
Tool abuseAgentic / MCP
Published CVSSCVE-2026-50548 · CVSS 4.0 Base 9.3 Critical · GitHub_MCVE-2026-50549 · CVSS 4.0 Base 9.3 Critical · GitHub_M
Cp is recorded as the specification default rather than as corroborated, and that distinction is the point of the case. The failure is real and reproducible, but it terminates inside the document: nothing…
Tool-calling LLM
CVSS — no applicable published score verified
Indicative ERS6.0range 2.3–9.7
MVT evidenceMVT floor: at least Minor
2026-08-24 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Popularity is not provenance. Ro-5 scores 0.00 not because the skill was malicious when reviewed — it was not — but because the admission decision was never bound to the bytes it approved, so an install…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.8range 3.8–10.0
MVT evidenceMVT floor: at least Minor
2026-08-24 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Miasma moves supply-chain execution from package installation to project open, and AITBM records that as an identity failure as much as a containment one: Cn-5 scores 0.00 because nothing bound the agent's…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.9range 3.9–10.0
MVT evidenceMVT floor: at least Major
2026-08-24 · AIDEFEND in Action · Traditional ML / Classifier · Tier 3
Three boundaries each failed independently — an origin heuristic mistaken for identity, network reachability from a browser process to a management port, and an unauthenticated execution API — and the case…
Model pipeline
Published CVSSCVE-2025-62593 · CVSS 4.0 Base 9.4 Critical · GitHub_M
Indicative ERS4.5range 1.8–7.2
MVT evidenceMVT floor: at least Minor
2026-08-24 · AIDEFEND in Action · Traditional ML / Classifier · Tier 3
Cn-1 scores 0.25 rather than 0.00 even though the SSRF succeeded completely, because AITBM scores the boundary that exists rather than the outcome that occurred: MLflow did have a destination policy and it…
Data exposureModel pipeline
Published CVSSCVE-2026-64849 · CVSS 3.1 Base 8.6 High · MLflow / GitHub maintainer advisory
A denylist is not an admission gate. The control that was present ran on every snippet and still scored only 0.25, because Cn-3 measures survival under systematic evasion and eight independent working…
Prompt injectionTool abuseTool-calling LLM
Published CVSSCVE-2026-70477 · CVSS 4.0 Base 9.5 Critical · GitHub_M
Indicative ERS5.5range 2.4–8.7
MVT evidenceMVT indeterminate
2026-08-12 · AIDEFEND in Action · Agentic / MCP System · Tier 1
MCP onboarding cannot be a one-time trust decision: clients must bind descriptor and prompt semantics, detect drift, and re-authorize every consequential action against current user intent.
Supply-chain compromiseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.8range 3.9–9.7
MVT evidenceCritical MVT confirmed
2026-08-12 · AIDEFEND in Action · Agentic / MCP System · Tier 1
Opaque state is not safe state: reasoning artifacts need confidentiality, principal/session binding, bounded retention, and an output gate before they enter logs or client-visible trajectories.
A chatbot with no tools at all can still reach Cp = 1.00 on corroborated evidence when its output is persisted into a privileged downstream renderer: the risk sits in Cn-3's unsanitised output, not in the…
A content filter that blocks the first attempt but yields to iterative rewording is a 0.25 control, and on a hosted service it fails together with credential binding: Storm-2139 needed both a leaked key and…
Tool metadata is instruction input: a docstring alone moved an agent from a benign request to reading an SSH private key and exfiltrating it in a tool argument, so AITBM scores the receiving client (Cn-8,…
A tool supply-chain compromise can bypass the model entirely: the BCC was added in server code, so no prompt-injection or output control could have seen it, and AITBM places the evidence on Ro-5, Tr-4, Cn-1…
A human-approval gate is only as strong as the authority that can switch it off: OpenClaw's dangerous-command prompt and sandbox were real, so Cn-1 and Cn-6 sit at 0.25 rather than 0.00, but because the…
Agentic / MCP
Published CVSSCVE-2026-25253 · CVSS 3.1 Base 8.8 High · mitre
A confirmation gate that fired every time still let 16 users run an attacker's command within 8 hours, because it showed no provenance and the domain was a lookalike: AITBM credits the gate (Cn-6 0.25, Aa…
A human confirmation prompt is a real control and lifts Cn-2 and Cn-6 to 0.25, but it gates a tool class, not a reversibility class: an obscured command carrying a delegated-irreversible credential…
Rules files are mutable behavioural state, so AITBM scores the backdoor through Ro-5 and Cn-5 (both 0.00) and applies the behavioural staleness window; the invisible Unicode defeats human review rather than…
Access control held and still leaked: Slack AI honoured every channel permission, which earns Cn-1 its 0.50, yet one authenticated member's public post steered the victim's authorised context into…
Prompt injectionData exposureRAG
CVSS — no applicable published score verified
Indicative ERS3.5range 1.6–5.3
MVT evidenceMVT indeterminate
2026-08-06 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Representative-configuration scoring lets an unnamed KYC deployment be scored without inventing a vendor: the observed defeat of passive and active liveness by camera-feed injection places Ro-1 at 0.25,…
Model pipeline
CVSS — no applicable published score verified
Indicative ERS3.6range 1.2–5.9
MVT evidenceMVT indeterminate
2026-08-06 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 3
A scanner that must fully deserialize an artifact to judge it sits on the wrong side of the code-execution boundary: the evasion holds Ro-5 at 0.25 only because a hub-side scan existed, while the loader…
Supply-chain compromiseModel pipeline
CVSS — no applicable published score verified
Indicative ERS3.7range 1.4–5.9
MVT evidenceMVT indeterminate
2026-08-06 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 3
When the namespace owner is the attacker, every downstream integrity control inherits a false root of trust: lineage, poisoning resistance, and scope fail at the same identity step, so the case lands on…
A retrieval-grounded answer can fail on integrity without any data leaving the tenant: the citation that is supposed to let a human verify Copilot's answer was dictated by the poisoned email it cited, which…
Self-replication is what separates Morris II from an ordinary RAG injection in AITBM terms: output that re-enters other assistants' retrieval stores corroborates Cp at 1.00 through unbounded fan-out and…
RAG
CVSS — no applicable published score verified
Indicative ERS6.3range 3.1–9.5
MVT evidenceMVT indeterminate
2026-08-06 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Shipping a model inside a client package moves its integrity boundary onto the device, and an app that loads that model without verification scores Ro-5 = 0.00 however accurate the clean model is; a single…
Model pipeline
CVSS — no applicable published score verified
Indicative ERS3.8range 1.2–6.4
MVT evidenceMVT indeterminate
2026-08-06 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
An AI supply-chain exposure with no model-level attack is scored on the escalation and workload-identity controls that failed (Cn-2 and Cn-5 at 0.25), while the training-data and release tampering the…
Observability metadata is routing authority when it can select an exporter; trace context must be schema-restricted, destination-pinned, and minimized before export.
Tool-calling LLM
Published CVSSCVE-2026-25528 · CVSS 3.1 Base 5.8 Medium · GitHub_M
Indicative ERS4.1range 1.7–6.5
MVT evidenceMVT indeterminate
2026-08-05 · AIDEFEND in Action · Standalone LLM / Generative AI · Tier 1
An internal AI message bus is still an untrusted code boundary: peer identity, segmentation, and safe serialization must hold before bytes reach a deserializer.
Tool abuseTool-calling LLM
Published CVSSCVE-2026-3059 · CVSS 3.1 Base 9.8 Critical · CISA-ADPCVE-2026-3060 · CVSS 3.1 Base 9.8 Critical · CISA-ADP
Serialized conversation history is active authority when deserialization triggers I/O; replay paths require the same destination policy as an explicit network tool call.
Tool-calling LLM
Published CVSSCVE-2026-25580 · CVSS 3.1 Base 8.6 High · GitHub_M
Indicative ERS4.6range 1.7–7.6
MVT evidenceMVT indeterminate
2026-08-05 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Long-term memory is persistent control input: every write needs provenance and promotion policy, and every recall must be re-authorized against the current task before it can influence tools.
A provenance heuristic keyed to the turn in which untrusted data arrives is a real control and earns Cn-2 = 0.25, but once a one-word reply can move the instruction past it, the path to physical and…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS5.8range 2.2–9.4
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Model extraction from a client application is scored on Pr-2 since its 2026-10-14 revision: unprotected models shipped in the package set the placement at 0.00 even though encryption forced runtime…
A hosted model's caller identity and its extraction monitoring are both security controls: when one actor can operate thousands of authenticated accounts behind resale proxies, authentication and regional…
A computer-use agent's clipboard and terminal are tools like any other: AITBM scores AI ClickFix as a Containment collapse (Cn-1, Cn-2 and Cn-6 at 0.00) rather than a perception error, because the decisive…
An attack that never ran can still be scored, but only where it was observed: the poisoned commit-to-release path yields Ro-5 and Cn-5 at 0.25, while every agent-side Containment sub-metric stays UNKNOWN…
Supply-chain compromiseAgentic / MCP
Published CVSSCVE-2025-8217 · CVSS 4.0 Base 5.1 Medium · AMZN
A guardrail the attacker has to talk past still earns Ro-1 0.25, but it moves no Containment score: with an ungated, sudo-capable shell, one successful jailbreak converts directly into irreversible…
A visible notification is not an integrity control: the 'memory set' notice keeps Tr-3 at 0.25, but the memory channel itself accepted untraceable externally sourced writes at Ro-4 = 0.00, and that…
'Living off AI' is a Cn-2 failure with a working role model underneath it: Jira's portal separation forced the attacker through the engineer's AI session, which earns 0.25 rather than 0.00, but an unscoped…
A control that gates tools by the turn in which untrusted data arrives, rather than by the provenance of the instruction being executed, earns credit as an existing check (Cn-2 = 0.25) but not as an…
For a hosted model service the decisive control is credential binding, not the model: authorisation worked as designed, yet a replayable credential plus an error-oracle side channel let attackers confirm…
Crediting a held control once and only once: Bard's CSP genuinely forced a bypass and earns Cn-1 its 0.50, but because it governs destinations rather than output content it does not also lift Cn-3, where…
A single injected page fails Cn-1 on two separate scope paths at once — the renderer's network destination and the model's tool selection — and both automated actions ran ungated, which is why Cn-6 sits at…
When the exfiltration hop is a user-followed link rather than an automatic fetch, the risk moves out of Autonomy Amplification (0.00) and into Robustness and Output Filtering, so a purely conversational…
A targeted weight edit that moves aggregate benchmark accuracy by 0.1% is invisible to benchmark-based acceptance, so model supply-chain risk must be scored on provenance binding and targeted behavioural…
Supply-chain compromiseTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS3.1range 1.1–5.1
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Identity-verification fraud is scored on the document-authenticity and face-match controls that were defeated, not on the downstream payout: a low-cost forgery-and-disguise technique places Ro-1 at 0.25,…
The case is the clearest Cn-7 failure in the batch: a one-line 'compute forever' prompt produced an unbounded loop that only a host restart ended, so Cn-7 is scored on observed evidence at 0.00 rather than…
Prompt injectionTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS5.7range 2.3–9.1
MVT evidenceMVT floor: at least Minor
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Keeping the classifier server-side denies white-box access but not evasion: client-side feature disclosure plus an unthrottled verdict oracle were enough for a transfer attack that evaded the production…
Online learning turns every public message into a training write: with no admission gate on the feedback loop, AITBM scores the poisoning (Ro-4), the echo path (Cn-3), and the representational harm (Fa-3)…
Tool-calling LLM
CVSS — no applicable published score verified
Indicative ERS6.1range 2.6–9.6
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
Returning raw model scores to the sender is a Cn-4 side channel that turns a black-box classifier into a trainable oracle; the resulting copy is a Pr-2 extraction failure, and it is what makes the Ro-1…
Model pipeline
Published CVSSCVE-2019-20634 · CVSS 3.1 Base 3.7 Low · mitre
Model extraction and adversarial transfer form one chain, not two findings: a replica built from ordinary public outputs became the staging ground for production evasion, so AITBM records the extraction on…
Tool-calling LLM
CVSS — no applicable published score verified
Indicative ERS4.1range 1.5–6.6
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
A biometric verification failure with large real-world fraud still yields one directly observed sub-metric: AITBM scores the liveness control that was defeated (Ro-1 0.25), carries the USD 77 million…
Tool abuseModel pipeline
CVSS — no applicable published score verified
Indicative ERS3.6range 1.2–5.9
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 2
An ensemble whose secondary reputation model can override the primary classifier inherits the weaker model's robustness, and a log channel that exposes decision internals turns that weakness into a…
Supply-chain compromiseModel pipeline
CVSS — no applicable published score verified
Indicative ERS5.1range 2.1–8.1
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND in Action · Agentic / MCP System · Tier 1
Model weights are only one executable release component; chat templates must be digest-bound, provenance-checked, and security-regression-tested with the same rigor as the weights.
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS4.8range 1.9–7.7
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND in Action · Standalone LLM / Generative AI · Tier 1
A familiar model name is not an identity: deployment admission must bind approved bytes, signer, source ownership, and loader policy before first load and every reload.
Supply-chain compromiseTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS4.0range 1.7–6.4
MVT evidenceMVT indeterminate
2026-08-02 · AIDEFEND in Action · Agentic / MCP System · Tier 1
Persistent memory changes prompt injection from a one-chat event into delayed control flow; trusted intent must govern both memory promotion and every later rehydration.
Prompt injectionData exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.0range 2.6–9.3
MVT evidenceCritical MVT confirmed
2026-08-02 · AIDEFEND in Action · Agentic / MCP System · Tier 1
A sandbox is only as strong as its least-governed sibling tool: the Bash boundary held, but the in-process Read path crossed the same CI-secret boundary without equivalent enforcement.
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS5.8range 2.8–8.8
MVT evidenceMVT floor: at least Minor
2026-07-27 · AIDEFEND in Action · Agentic / MCP System · Tier 3
A platform can ship an approval gate and still score Cn-6 = 0.00 when that gate is writable by the very workflow it governs — AITBM scores the exercised configuration, not the nominal capability — and…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.3range 4.2–10.0
MVT evidenceMVT floor: at least Major
2026-07-22 · AIDEFEND in Action · Agentic / MCP System · Tier 1
Re-derived against OpenAI's 26 August end-to-end report, the case moves in two directions at once and neither is a metadata bump. Cn-4 falls from 0.25 to 0.00 because what the earlier account recorded as…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.2range 5.0–9.3
MVT evidenceCritical MVT confirmed
2026-07-11 · AIDEFEND in Action · Agentic / MCP System · Tier 2
A human-approval gate only counts for as much of the chain as it actually governs: Notion's page-edit approval was real enough to raise Aa to 0.50 and hold Cn-6 above zero, yet the render hop that fired…
A local AI runtime's updater is part of its supply chain: a no-op signature check and an unconstrained staging path place the case at Ro-5 = 0.00 and Cn-1 = 0.25 without any model being touched, while a…
Tool abuseTool-calling LLM
Published CVSSCVE-2026-42248 · CVSS 4.0 Base 7.7 High · CERT-PLCVE-2026-42249 · CVSS 4.0 Base 7.7 High · CERT-PL
Indicative ERS3.5range 1.2–5.8
MVT evidenceMVT indeterminate
2026-07-07 · AIDEFEND SecureFlow · Traditional ML / Classifier · Tier 1
A serving runtime's own error path can hand an unauthenticated caller the key to its private memory: Cn-4 and Cn-5 at 0.00 and Cn-1 at 0.25 show that information leakage, caller identity, and API scope…
Tool abuseModel pipeline
Published CVSSCVE-2025-23319 · CVSS 3.1 Base 8.1 High · nvidiaCVE-2025-23320 · CVSS 3.1 Base 7.5 High · nvidiaCVE-2025-23334 · CVSS 3.1 Base 5.9 Medium · nvidia
A mode-selection fallback is a privilege decision: Atlas scores Cn-2 0.25 because ambiguous omnibox input was elevated to the most trusted role, yet with only a navigation demonstrated Cp stays at the…
Prompt injectionAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS3.7range 1.1–6.3
MVT evidenceMVT indeterminate
2026-07-07 · AIDEFEND in Action · Multi-Agent / MCP System · Tier 2
This is the reference case for cp_basis = default: the agents are maximally exposed and their navigation action is entirely ungated, yet the measured terminal impact is a benign HTTP request, so Cp = 1.00…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.1range 2.8–10.0
MVT evidenceMVT indeterminate
2026-07-07 · AIDEFEND in Action · Agentic / MCP System · Tier 2
AgentFlayer is the batch's clearest case of a control that half-held changing two scores at once: because a URL reputation check existed and had to be bypassed, Cn-3 sits at the rubric's bypass anchor…
Prompt injectionData exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS5.8range 2.7–8.9
MVT evidenceMVT floor: at least Minor
2026-07-07 · AIDEFEND in Action · Agentic / MCP System · Tier 2
This is the cleanest Cn-6 = 0.00 in the set and shows why AITBM separates Cn-6 from Cn-1: the agent never exceeded its granted CRM permissions, so a permission-only assessment would find nothing wrong, yet…
Prompt injectionTool abuseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.2range 2.2–10.0
MVT evidenceMVT indeterminate
2026-07-07 · AIDEFEND in Action · Agentic / MCP System · Tier 2
This case shows the Behavioral Attestation Window being correctly withheld: the agent is unambiguously Agentic and scores at the ORP ceiling, but none of the four BAW checklist items is evidenced for a…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.7range 2.9–10.0
MVT evidenceMVT indeterminate
2026-07-06 · AIDEFEND in Action · Agentic / MCP System · Tier 2
LangGraph is the cleanest available demonstration that agent memory is an Ro-4 poisoning surface rather than a storage detail: an attacker-planted checkpoint row promoted straight into trusted agent state…
Two AITBM behaviours meet in this case: As sitting exactly on 0.75 keeps N_elevated at one and CRM at 1.00 even though the cascade path is corroborated all the way to a credential-issuing node, and…
Data exposureTool abuseTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS3.8range 1.3–6.3
MVT evidenceMVT indeterminate
2026-07-06 · AIDEFEND in Action · Multi-Agent / MCP System · Tier 3
A loopback-bound control plane is not a lower-exposure deployment: because a browsing agent renders untrusted content on the same host, As reaches the 1.00 anchor and the Cp path is corroborated end-to-end…
Tool abuseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS5.6range 2.4–8.7
MVT evidenceMVT indeterminate
2026-07-06 · AIDEFEND in Action · Agentic / MCP System · Tier 3
This is the batch's only case with no patch to point at, and it lands where AITBM says it should: Rf = 0.75 rather than 0.00 because every remedy is an external containment layer, while Cn-6 = 0.00 for a…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.0range 4.5–9.4
MVT evidenceMVT floor: at least Minor
2026-07-06 · AIDEFEND in Action · Agentic / MCP System · Tier 2
PerplexedBrowser is the case where the assessed system's own security controls were largely irrelevant to the outcome: the vault held, the model filter partly held, and the system still failed — because…
Tool abuseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.4range 3.3–10.0
MVT evidenceMVT floor: at least Minor
2026-07-06 · AIDEFEND in Action · Agentic / MCP System · Tier 3
When a client treats repository content as configuration, the poisoning surface is the tool manifest rather than the model — Ro-5 and Cn-5 both collapse to 0.00 on the same evidence, and a shipped,…
Data exposureTool abuseAgentic / MCP
Published CVSSCVE-2026-12957 · CVSS 4.0 Base 8.5 High · AMZN
DifyTap is the case that separates audit-trail completeness from audit-trail safety: Tr-3 field coverage was strong enough for the 0.75 band and still capped at 0.50, because the 0.75 criterion requires the…
Data exposureTool-calling LLM
Published CVSSCVE-2026-41949 · CVSS 4.0 Base 8.2 High · VulnCheck CNA
Indicative ERS4.9range 2.2–7.5
MVT evidenceMVT indeterminate
2026-07-06 · AIDEFEND in Action · Agentic / MCP System · Tier 1
JADEPUFFER is the case that forces the assessor to keep the attacker out of the assessed system: the agentic behaviour that compressed the kill chain to 31-second self-repair belonged to the offence, so it…
Tool abuseAgentic / MCP
Published CVSSCVE-2025-3248 · CVSS 3.1 Base 9.8 Critical · VulnCheck
An AI gateway with no agents, no memory and no autonomy still classifies as Connected GenAI and still forces Cp = 1.00 on its merits — because the corroborating path runs through a credential-issuing (P4)…
Tool-calling LLM
Published CVSSCVE-2026-40217 · CVSS 3.1 Base 8.8 High · mitre
Indicative ERS4.8range 2.0–7.5
MVT evidenceMVT indeterminate
2026-07-02 · AIDEFEND in Action · Standalone LLM / Generative AI · Tier 3
Architecture class is scored on the assessed boundary, not on the attacker's behaviour: the exposed backend is a Standalone LLM with Aa = 0.25 and baw/agentic both false, yet three Containment sub-metrics…
When a backdoor lives in model-writable memory, the egress fix and the persistence fix are different remediations: closing the font-src channel under CVE-2026-24299 does not retire the unaudited…
Data exposureAgentic / MCP
Published CVSSCVE-2026-24299 · CVSS 3.1 Base 5.3 Medium · microsoft
An approval policy can exist and still be the failure point: exempting self-addressed messages from approval is a real Cn-6 classification (0.25, not 0.00), but because the exempted hop is the one that…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS5.9range 2.9–8.9
MVT evidenceMVT floor: at least Minor
2026-06-27 · AIDEFEND in Action · Multi-Agent / MCP System · Tier 3
Detection capability and evidence freshness are scored in different layers, and this case separates them cleanly: the monitor's blindness is a point-in-time IVP finding at Ro-1 and Cn-3, while the same…
This is the clean illustration of cp_basis = 'default' versus 'corroborated': all four stack layers were reachable and data did leave the tenant, but every terminal node in the observed path was…
Data exposureTool-calling LLM
Published CVSSCVE-2026-42824 · CVSS 3.1 Base 6.5 Medium · microsoft
Indicative ERS4.8range 2.3–7.3
MVT evidenceMVT indeterminate
2026-06-22 · AIDEFEND in Action · Agentic / MCP System · Tier 3
A tool integration that is read-only by design can still drive an agent to code execution: the boundary that failed is the MCP output boundary, not the model, which is why Ro-1 stays at 0.25 while five…
Forever Security demonstrated that an attacker page could dispatch a synthetic drag event to Sider, causing it to embed an authenticated Gemini page after weakening iframe restrictions. Through an open…
Tool-calling LLM
Published CVSSSpyder-Sider-research · CVSS 10.0 (version and metric group not stated by source) Critical · Forever Security Research
Forever Security demonstrated that a webpage could forge the expected MaxAI message marker and cause the content script to forward arbitrary function names and arguments to a privileged background API…
Tool-calling LLM
Published CVSSMaXSS-MaxAI-research · CVSS 10.0 (version and metric group not stated by source) Critical · Forever Security Research
Indicative ERS4.0range 1.1–6.9
MVT evidenceMVT indeterminate
2026-06-09 · AIDEFEND in Action · Agentic / MCP System · Tier 2
A confirmation gate that exists but is not bound to a canonical action summary earns Cn-6 = 0.25, not credit for human-in-the-loop control — and because the gate cannot be claimed at CBR >= 0.95, the same…
Cascade Potential can legitimately be a default rather than a corroborated 1.00: the injected content traverses all four stack layers, but the terminal node is an external fetch rather than a write-external…
Tool-calling LLM
CVSS — no applicable published score verified
Indicative ERS4.9range 2.5–7.3
MVT evidenceMVT floor: at least Minor
2026-06-01 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Ro-4 poisoning resistance is not only about training data and RAG corpora: an agent's own instruction and configuration files are an ingestion channel, and where they are read as authoritative guidance with…
Data exposureSupply-chain compromiseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.0range 4.3–9.7
MVT evidenceMVT floor: at least Minor
2026-05-27 · AIDEFEND in Action · Multi-Agent / MCP System · Tier 1
Authentication is not authorisation: a cryptographically valid, correctly authenticated peer session still scores Cn-5 low, because Cn-5 measures whether identity is bound to instruction provenance and tool…
Agentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.9range 4.0–10.0
MVT evidenceCritical MVT confirmed
2026-05-26 · AIDEFEND in Action · RAG / Retrieval-Augmented System · Tier 3
Remediation Feasibility sits at its bottom anchor — a patchable ordering bug with a CVE and a fixed release — while Cascade Potential still forces 1.00, which is exactly the layer separation AITBM is built…
Tool abuseRAG
Published CVSSCVE-2026-45829 · CVSS 4.0 Base 10.0 Critical · HiddenLayer
Indicative ERS4.8range 2.7–6.9
MVT evidenceMVT indeterminate
2026-05-15 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Nothing in this case reaches the model — there is no prompt, no injection, and no Robustness-1 signal at all — so AITBM's not-applicable redistribution rule carries the whole assessment on Containment,…
Persistent instruction files turn one indirect prompt injection into a standing implant: AITBM records the injection on Ro-1 (0.25) and the poisoned, re-ingested system-prompt file separately on Ro-4…
Prompt injectionAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS7.4range 3.1–10.0
MVT evidenceMVT indeterminate
2026-05-08 · AIDEFEND in Action · Agentic / MCP System · Tier 3
The adversary never touched the model — it optimised the documentation the model reads — so the scoring weight lands on Ro-5 ingestion integrity and Cn-1/Cn-6 execution gating rather than on jailbreak…
Supply-chain compromiseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.1range 3.9–8.4
MVT evidenceMVT indeterminate
2026-05-03 · AIDEFEND in Action · Agentic / MCP System · Tier 3
The exploited input never reached the model, which is exactly why Ro-1 must be scored over the agent's whole task-setup surface rather than its prompt: an agent's adversarial-input resistance is only as…
Data exposureAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS4.0range 1.9–6.1
MVT evidenceMVT indeterminate
2026-05-03 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Containment can score 0.00 on an AI product whose model behaved perfectly: the assessed boundary here is the extension host and the credential store, so a client-side trust-boundary failure lands squarely…
Data exposureSupply-chain compromiseAgentic / MCP
Published CVSSCursorjacking · CVSS 8.2 (version and metric group not stated by source) High · LayerX Security
Indicative ERS4.2range 2.2–6.2
MVT evidenceMVT indeterminate
2026-05-03 · AIDEFEND in Action · Agentic / MCP System · Tier 3
There is no adversary in this case at all, and AITBM still scores it as a Containment collapse — Cn-1, Cn-2 and Cn-6 are driven by what the agent was technically able to do, not by whether anyone attacked…
Tool abuseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS4.8range 2.0–7.7
MVT evidenceMVT indeterminate
2026-04-29 · AIDEFEND in Action · Agentic / MCP System · Tier 1
An AI system can fail the Containment axis with no model in the loop at all: Cn-5 is scored on the enforced authorization boundary around agent identities, so a directory role whose documented scope and…
Tool abuseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS3.8range 1.3–6.3
MVT evidenceMVT indeterminate
2026-04-29 · AIDEFEND in Action · RAG / Retrieval-Augmented System · Tier 2
An incident with no established root cause is still scorable — the enforced boundary and the missing release gate are directly observable from the outcome — and the unresolved mechanism belongs in ACI (thin…
Data exposureRAG
CVSS — no applicable published score verified
Indicative ERS3.5range 1.4–5.6
MVT evidenceMVT indeterminate
2026-04-25 · AIDEFEND in Action · Agentic / MCP System · Tier 2
A population study can be scored honestly as a representative configuration, but only if the assurance layer carries the cost: Pc = 0.10 and a class-level Cp classified as default rather than corroborated…
Prompt injectionAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.4range 3.0–9.8
MVT evidenceMVT indeterminate
2026-04-25 · AIDEFEND in Action · Agentic / MCP System · Tier 3
Authentication succeeded and the provider's write boundary held, so the failure has to be located precisely rather than described as 'broken identity': AITBM puts it in Cn-5 = 0.40 (a valid managed token…
Controls that held move the numbers as much as the ones that failed: a measured 76% attack success rate coexists with Cn-1 and Cn-2 at 0.50 (the OS app sandbox bounded the blast radius) and Rf at 0.25 (a…
Prompt injectionTool abuseTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS3.9range 1.8–6.1
MVT evidenceMVT indeterminate
2026-04-25 · AIDEFEND in Action · Agentic / MCP System · Tier 3
The trust boundary that fails here is neither the model nor the tool but the transport intermediary between them, and AITBM localises it precisely — Cn-5 = 0.25 for an unverifiable response origin under…
Supply-chain compromiseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS8.0range 5.4–10.0
MVT evidenceMVT indeterminate
2026-04-24 · AIDEFEND in Action · Traditional ML / Classifier · Tier 3
An artifact-supply-chain incident with no agent, no prompt and no model output is still fully scorable — the evidence lands on Ro-5, Tr-3/Tr-4 and Cn-1/Cn-2 — and because the assessed configuration was…
Model pipeline
CVSS — no applicable published score verified
Indicative ERS5.0range 2.6–7.4
MVT evidenceMVT indeterminate
2026-04-23 · AIDEFEND in Action · RAG / Retrieval-Augmented System · Tier 2
This is the batch's clearest demonstration that a control which held still gets scored, and scored up: CSP blocked the direct egress domain and the XPIA classifier forced the attacker to craft plain prose,…
Data exposureRAG
Published CVSSCVE-2025-32711 · CVSS 3.1 Base 9.3 Critical · microsoft
Indicative ERS4.3range 1.9–6.7
MVT evidenceMVT indeterminate
2026-04-22 · AIDEFEND in Action · Agentic / MCP System · Tier 3
The scoring turns on an evidentiary rule rather than a judgement call: the 0.50 Ro-1 anchor describes this case qualitatively — common attacks resisted, multi-step tool-mediated attacks still effective —…
AITBM scores a software supply-chain compromise as an AI-system finding without distorting either: the AI-specific signal lands on Ro-5 (the dependency ingestion path is a poisoning channel), Cn-5 (static…
Supply-chain compromiseTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS4.3range 1.8–6.9
MVT evidenceMVT indeterminate
2026-04-18 · AIDEFEND in Action · Agentic / MCP System · Tier 2
A containment control can hold and the deployment still be compromised: the agent sandbox blocked in-runtime execution, which is why Cn-1 is scored up to 0.50 rather than down at a failure anchor, while the…
Supply-chain compromiseAgentic / MCP
CVSS — no applicable published score verified
Indicative ERS6.0range 2.8–9.1
MVT evidenceMVT floor: at least Minor
2026-04-18 · AIDEFEND in Action · Agentic / MCP System · Tier 2
Cn-5 is the case's hinge and shows why a mechanism-only reading of the rubric is wrong: the gateway had real authentication (pairing, device tokens, a password), which is the 0.25 anchor, but the measured…
Identity, not the model, is the AI attack surface here: every low sub-metric sits in Containment (Cn-1, Cn-2, Cn-4, Cn-5, Cn-6 all at or near the floor) while Robustness barely features - and the case is…
Data exposureTool-calling LLM
CVSS — no applicable published score verified
Indicative ERS5.5range 3.1–7.9
MVT evidenceMVT floor: at least Major
2026-04-17 · AIDEFEND in Action · RAG / Retrieval-Augmented System · Tier 3
The sub-metric that should have stopped this is Ro-4, not a web-application control: once the prompt and retrieval tables were writable, the AI platform's integrity depended on chunk and configuration…
RAG
CVSS — no applicable published score verified
Indicative ERS4.5range 2.2–6.7
MVT evidenceMVT indeterminate
2026-04-16 · AIDEFEND in Action · Agentic / MCP System · Tier 2
ForcedLeak shows why Cp = 1.00 here is corroborated rather than defaulted: a sink gate that a researcher's payload was observed crossing cannot be claimed at CBR >= 0.95, so the path counts as ungated to a…
Prompt injectionData exposureTool abuse
Published CVSSForcedLeak · CVSS 9.4 (version and metric group not stated by source) Critical · Noma Security
Indicative ERS7.6range 3.7–10.0
MVT evidenceMVT floor: at least Minor
2026-04-16 · AIDEFEND in Action · Agentic / MCP System · Tier 3
A case with no exploit still moves the AITBM score: a change to an agent's authority boundary trips the C_event <= 0.35 cap and, with mutable behavioural state, the M_Em = 3.0 behavioural staleness floor -…
Microsoft reproduced a prompt-to-host command path in Semantic Kernel Python when a SearchPlugin input reached an InMemoryVectorStore filter built with eval(). The blocklist and empty builtins did not stop…
Tool abuseTool-calling LLM
Published CVSSCVE-2026-26030 · CVSS 3.1 Base 9.9 Critical · Microsoft Semantic Kernel maintainer advisory
Microsoft found that SessionsPythonPlugin DownloadFileAsync was exposed to model calls and accepted an AI-controlled localFilePath with no path restriction. In a controlled chain, the model created a script…
Agentic / MCP
Published CVSSCVE-2026-25592 · CVSS 3.1 Base 9.9 Critical · Microsoft Semantic Kernel maintainer advisory
The agent had a nominal workspace write boundary, but changing multi-root folders and settings could extend that boundary and activate an executable path. The AITBM anchor applies only to the stated product…
Agentic / MCP
Published CVSSCVE-2025-64660 · CVSS 3.1 Base 8.0 High · Microsoft CNA
Cursor had protected some editor-sensitive files, but a .code-workspace file could be modified without that approval. The AITBM anchor applies only to the stated product and configuration.
Agentic / MCP
Published CVSSCVE-2025-61590 · CVSS 3.1 Base 7.5 High · GitHub maintainer CNA
Roo Code protected .vscode writes but did not apply the same approval to .code-workspace under the documented auto-approval configuration. The AITBM anchor applies only to the stated product and configuration.
Agentic / MCP
Published CVSSCVE-2025-58372 · CVSS 3.1 Base 8.1 High · GitHub maintainer CNA
Zed limited writes outside the project and normally required terminal approval, but a project-local settings write let the agent disable that approval. The AITBM anchor applies only to the stated product…
Agentic / MCP
Published CVSSCVE-2025-55012 · CVSS 4.0 Base 8.5 High · GitHub maintainer CNA
Cursor protected edits to existing dotfiles but did not apply the same approval gate to creating a new sensitive editor settings file. The AITBM anchor applies only to the stated product and configuration.
Agentic / MCP
Published CVSSCVE-2025-54130 · CVSS 3.1 Base 7.5 High · GitHub maintainer CNA
Roo Code had an approval system, but with Write auto-approval enabled it did not protect .vscode/settings.json from agent writes. The AITBM anchor applies only to the stated product and configuration.
Agentic / MCP
Published CVSSCVE-2025-53536 · CVSS 3.1 Base 8.1 High · GitHub maintainer CNA
A workspace read boundary existed, but search_files failed to enforce it; prompt influence could reach an outside file and schema-fetch URL. The AITBM anchor applies only to the stated product and…
Agentic / MCP
Published CVSSCVE-2025-53097 · CVSS 3.1 Base 5.9 Medium · GitHub maintainer CNA
The default schema fetch followed a model-influenced JSON write to an arbitrary external URL without a per-request authorization gate. The AITBM anchor applies only to the stated product and configuration.
Agentic / MCP
Published CVSSCVE-2025-49150 · CVSS 3.1 Base 5.9 Medium · GitHub maintainer CNA
MetaGPT 0.7.3 metagpt.strategy.tot.TreeofThought is one bounded prompt-to-code research path. The paper reports this CVE and 8.4 but no complete original vector was verified.
Lagent 0.1.1 lagent.actions.PythonInterpreter is one bounded prompt-to-code research path. The paper reports this CVE and its tested version; no complete primary CVSS vector was verified.
Griptape 0.17.1 griptape.tools.Calculator is one bounded prompt-to-code research path. The paper reports this CVE and its tested version; no complete primary CVSS vector was verified.
vanna 0.3.3 vanna.ask is one bounded prompt-to-code research path. The huntr CNA record corroborates the ask() prompt-injection path and provides exact CVSS 3.0 metadata.
Tool-calling LLM
Published CVSSCVE-2024-5826 · CVSS 3.0 Base 9.8 Critical · huntr CNA
LlamaIndex 0.7.13 PandasQueryEngine.query is one bounded prompt-to-code research path. The documented 0.7.13 path is scored; a separate third-party fix bypass is held.
LangChain 0.0.232 create_csv_agent, create_spark_dataframe_agent, and create_pandas_dataframe_agent is one bounded prompt-to-code research path. Three dataframe agent API rows share one CVE and unchecked…
In early July 2026, an unknown Chinese-language operator used a multi-agent framework built on Hermes and OpenClaw against government systems that subsequent public reporting identified as Taiwanese. Dream Rese
Anthropic reported a September 2025 campaign that used Claude Code, its AI coding agent, against roughly 30 organizations and compromised a small number. Anthropic attributes GTG-1002 to a Chinese state-sponsor
Rebora disclosed two different browser-extension privilege crossings in two different products. Spyder abused Sider's synthetic drag and cross-origin gesture path: an attacker page dispatched a dragstart event
SentinelLABS analyzed macOS.Gaslight, a Rust backdoor containing an approximately 3,500-byte prompt-injection payload with 38 fabricated system messages. The messages imitate an LLM-assisted malware-triage harn
Check Point Research demonstrated an "AI in the Middle" attack in which malware can abuse web-based AI assistants with anonymous or unauthenticated browsing and URL-fetch capabilities as a covert command-and-co
Researchers identified 20 remote code execution (RCE) vulnerabilities across 11 different LLM frameworks. They discovered applications deployed on the public internet built using these LLM frameworks and demons
The Microsoft Incident Response - Detection and Response Team (DART) investigated a compromised system where a threat actor utilized SesameOp, a backdoor implant that abuses the OpenAI Assistants API as a cover
Researchers at Lumia have demonstrated that it is possible to extract authentication tokens from the memory of LLM Desktop Applications. An attacker could then use those tokens to impersonate the victim to the
Cato CTRL security researchers have identified ProKYC, a deepfake tool being sold to cybercriminals as a method to bypass Know Your Customer (KYC) verification on financial service applications such as cryptocu
MITRE's AI Red Team demonstrated a physical-domain evasion attack on a commercial face identification service with the intention of inducing a targeted misclassification. This operation had a combination of tra
hCaptcha Threat Analysis Group (hTAG) tested 20 abuse scenarios against ChatGPT Atlas, Claude Computer Use, Gemini Computer Use, Manus AI, and Perplexity Comet. In the reported configurations, agents frequently
Orca found Internet-exposed vector databases containing source text, personal data, medical records, credentials, and internal configuration, then validated that credentials from one support-ticket index could
IDEsaster is a cross-product vulnerability class in which prompt injection does not need a dangerous agent tool to finish the attack. The agent uses ordinary file access, then the underlying IDE automatically l
In July 2025, Ukrainian authorities reported the emergence of LAMEHUG, a new AI-powered malware attributed to the Russian state-backed threat actor APT28 (https://attack.mitre.org/groups/G0007/) (also tracked a
Check Point Research identified a prototype malware sample in the wild that contained a prompt injection, which appeared to be designed to manipulate LLM-based malware detectors and/or analysis tools. However,
Researchers at Trend Micro, Inc. used service indexing portals and web searching tools to identify over 8,000 misconfigured private container registries exposed on the internet. Approximately 70% of the registr
Many recent large-scale datasets are distributed as a list of URLs pointing to individual datapoints. The researchers show that many of these datasets are vulnerable to a "split-view" poisoning attack. The atta
Researchers identified that large language models such as ChatGPT can hallucinate fake software package names that are not published to a package repository. An attacker could publish a malicious package under
Google Colab is a Jupyter Notebook service that executes on virtual machines. Jupyter Notebooks are often used for ML and data science research and experimentation, containing executable snippets of Python code
Linux packages for PyTorch's pre-release version, called Pytorch-nightly, were compromised from December 25 to 30, 2022 by a malicious binary uploaded to the Python Package Index (PyPI) code repository. The mal
The Azure Red Team performed a red team exercise on a new Microsoft product designed for running AI workloads at the edge. This exercise was meant to use an automated system to continuously manipulate a target
The Microsoft AI Red Team performed a red team exercise on an internal Azure service with the intention of disrupting its service. This operation had a combination of traditional ATT&CK enterprise techniques su
OpenAI built GPT-2, a language model capable of generating high quality text samples. Over concerns that GPT-2 could be used for malicious purposes such as impersonating others, or generating misleading news ar
McAfee Advanced Threat Research noticed an increase in reports of a certain ransomware family that was out of the ordinary. Case investigation revealed that many samples of that particular ransomware family wer
The Palo Alto Networks Security AI research team was able to bypass a Convolutional Neural Network based botnet Domain Generation Algorithm (DGA) detector using a generic domain name mutation technique. It is a
The Palo Alto Networks Security AI research team tested a deep learning model for malware command and control (C&C) traffic detection in HTTP traffic. Based on the publicly available paper by Le et al. (https:/
Microsoft documented two distinct Semantic Kernel prompt-to-host-RCE paths: a Python Search Plugin filter evaluated with eval(), and a .NET SessionsPythonPlugin file-transfer function exposed to model tool call
ClawHub accepted and listed two TradingView-themed OpenClaw skills with malicious prerequisite instructions; at least one received an audit Pass. The redirection led to a Base64-encoded command that fetched a c
Harmonic analysed 22,458,240 enterprise GenAI prompts and file uploads across 665 tools and identified 579,113 sensitive exposures, with six applications accounting for 92.6% of them and ChatGPT alone for 71.2%
Sysdig observed an intrusion on May 10 2026 in which an attacker reached an internet-facing marimo notebook, gained command execution through CVE-2026-39987 on the /terminal/ws WebSocket, and then used an LLM a
This is a methodology source rather than an incident. The paper reframes indirect prompt injection as a system-architecture problem: an attacker hides instructions in an email, webpage, document, or tool output
This brief covers a research paper, not an incident. The paper separates the ML model from the ML system around it and argues that practical attackers frequently bypass several layers of that system rather than
Researchers showed that a student model can inherit a teacher model's behavioural traits from distillation data that carries no visible trace of the trait. A teacher is first nudged toward a preference (the pap
OpenAI confirms a Mixpanel breach affecting limited customer-identifiable analytics associated with some of its users, with a December clarification of the user scope.
No matching recordsTry a broader term or clear the active category.
Showing 1–10 of 156
Indicative ERS is a normalized-assurance comparison scenario
and must be read with its best-to-worst interval. Public ACI describes the article evidence package;
MVT reports only a severity floor proved across the uncertainty bounds.
Featured in the news
Renewed reporting makes this existing evidence-bounded ERS case relevant to the current news cycle. News selection does not change its assessment evidence or score.
FEATURED CASE
OpenAI Evaluation Agents and the Hugging Face Intrusion: Updated Technical Reconstruction
Re-derived against OpenAI's 26 August end-to-end report, the case moves in two directions at once and neither is a metadata bump. Cn-4 falls from 0.25 to 0.00 because what the earlier account recorded as one file-disclosure reference is now two independent unintended-read…
45 of the 201 records have no ERS, for one of
two reasons. 0 are awaiting analysis: their source must still be reviewed,
split into per-product records, or scored as the AI workload an infrastructure component serves.
45 have documented scoring limits: they may combine separately assessed
product paths, lack a bounded victim AI system, or omit the evidence needed for a complete rubric anchor.
Aggregate records link to their separate assessments where available. Every record follows the same
four-step scorability admission test (system, boundary, observation, multiplicity).
21 of the unscored records mirror AIDEFEND SecureFlow
attack flows and carry the ordered attack steps, ATLAS technique labels, and step-matched AIDEFEND
defenses. They remain available through the archive browsing mode.
Select Browse unscored records to search this archive in the directory above. Complete attack steps,
references, defenses, and scoring limitations are preserved on their individual record pages.
AppOmni research: identity and agent delegation
Research by Aaron Costello at AppOmni provides additional
examples for designing AI security evaluations. Browse his
AppOmni author archive
and the original technical disclosures below. Source selection checked 2 October 2026.
These supplementary studies are outside the counted
case library and have no ERS. The questions below are qualitative evaluation routes, not scored
findings or evidence of implemented controls. Each study describes its tested configuration at
disclosure time, rather than the current security posture of ServiceNow.
Aaron Costello · AppOmni · 13 January 2026 · CVE-2025-12420
A shared integration secret and email-based account linking
enabled user impersonation and privileged Now Assist workflows. The disclosure records vendor
remediation on 30 October 2025.
Evaluation questions
Is the agent's acting identity bound to an authenticated user across integration and account-linking boundaries? (Cn-5)
Can an alternate conversational entry point invoke privileged workflows outside the user's authorized scope? (Cn-1, Cn-2)
Attacker-controlled ticket content redirected an admin-invoked
Now Assist agent to recruit another agent and copy restricted ticket data into an attacker-readable
ticket, despite enabled prompt-injection protection. Tool and team configuration determined exposure.
Evaluation questions
Can ticket content redirect the task or expand delegated authority across agents? (Ro-1, Cn-1, Cn-2)
Are consequential tool actions classified before execution, with required human authority preserved across delegation? (Cn-6)
Score your own system
These cases work backwards from an incident. The same three layers
work forwards, before anything goes wrong — which is the point.
MVT — Minimum Viability Threshold. It is the per-tier minimum each assessed IVP axis must meet. A breach sets an independent severity floor, so Critical MVT does not automatically mean Critical ERS.