ASR AI Security Radar
Methodology Recent Incidents Get Notified

Back to incidents

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

Source disclosure: October 13, 2026 | Published on Radar: October 13, 2026 | Source: NVD | Classification confidence: 45%

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.

A security flaw has been discovered in TinyLLaVA TinyLLaVA Factory up to 1abc6ac5e76a68d0fd087a071b56da968e69ca9b. The impacted element is the function load text config of the file tinyllava/model/configuration tinyllava.py of the component TinyLlavaConfig. Performing a manipulation of the argument llm model name or path results in code injection.

Why This Is AI-Related

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

  • llm

Affected Workflow

Review the AI product, dependency, and integration points mentioned in the source advisory before broadening remediation.

Likely Attack Path

The advisory indicates a security path that can affect AI applications, assistants, models, or connected automation workflows if the component is deployed.

Impact

The advisory has meaningful security implications for an AI-related product, dependency, or workflow and should be triaged against deployed usage. Severity HIGH. Classification confidence 45%. Source channel NVD.

Detection And Triage Signals

  • New security events tied to the affected component or advisory identifier
  • Changes in AI workflow behavior, access logs, or plugin execution after the advisory window
  • Evidence that the vulnerable version is active in environments that process sensitive data

Recommended Response

  • Confirm whether affected products, models, or integrations are used in your environment.
  • Apply vendor fixes or mitigations and restrict risky permissions until verified.
  • Monitor logs for related indicators and document containment for audit evidence.

Compliance And Business Impact

Even when exploit details are still emerging, delayed triage can widen operational and compliance exposure around AI systems.

Sources

Want alerts like this in real time?

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

Get Notified

More incidents