ASR AI Security Radar
Methodology Recent Incidents Get Notified

Back to incidents

AI security incident: CVE-2026-44209 (NVD)

Source disclosure: May 26, 2026 | Published on Radar: October 13, 2026 | Source: NVD | Classification confidence: 55%

Source disclosure is when the advisory appeared in this source (or was added to a catalog), not a confirmed date of exploitation. Radar publication is when this page became available.

This incident is part of the public archive and includes explicit AI-related signals from the cited source material. Review methodology.

Banks generates meaningful LLM prompts using a template language that makes sense. Prior to 2.4.2, banks uses jinja2.Environment() (unsandboxed) to render prompt templates. Applications that pass user-supplied strings as the template argument to Prompt() are vulnerable to Server-Side Template Injection (SSTI), which can lead to Remote Code Execution (RCE) on the host system.

Why This Is AI-Related

This page is treated as AI-specific because the source material references llm, copilot, which places the issue inside an AI workflow, model, assistant, or supporting dependency rather than a generic software bulletin.

  • llm
  • copilot

Affected Workflow

Review AI plugins, copilots, model-serving helpers, CLI tools, and automation runtimes that execute system commands.

Likely Attack Path

An attacker can turn the vulnerable AI-adjacent component into a path for command execution on the host or service runtime.

Impact

The issue can create a path to command execution inside an AI-facing product, plugin, copilot, or supporting service runtime. Severity HIGH. Classification confidence 55%. Source channel NVD.

Detection And Triage Signals

  • New shell or process activity from AI-facing services
  • Unexpected outbound connections or file writes after prompt or API activity
  • Privilege changes, container escapes, or suspicious job execution logs

Recommended Response

  • Identify every environment that runs the affected AI plugin, assistant, CLI, or supporting package.
  • Patch or isolate the vulnerable component and remove risky execution permissions while validation is in progress.
  • Review process execution, outbound connections, and file-write logs for signs of post-exploitation activity.

Compliance And Business Impact

Code execution paths create immediate risk of host compromise, credential theft, and downstream lateral movement.

Sources

Want alerts like this in real time?

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents