Live AI Security Brief for July 30, 2026: Agents, Prompt Injection, and Model Risk

Live AI Security Brief for July 30, 2026: Agents, Prompt Injection, and Model Risk

Verified AI security news and advisories covering agent frameworks, prompt injection, tool access, sandboxing, model evaluation, and sensitive data boundaries.

Agent and model risk

AI security incidents increasingly cross the boundary between model output and real tools. The key review is not only what a model can say, but what its agent harness, connectors, credentials, network access, and execution environment allow it to do.

For July 30, 2026, the lead development is CVE-2026-55255: Langflow cross-user flow authorization bypass. Start by confirming where Langflow Langflow before 1.9.1 is deployed, who owns it, and whether the affected path is reachable. The remaining items below add the product-specific context needed to turn the headline into an owned security decision.

AI security developments

CVE-2026-55255: Langflow cross-user flow authorization bypass

NIST NVD and CISA KEV | July 7, 2026 | Known Exploited | CVSS 8.4 | Langflow Langflow before 1.9.1

Before version 1.9.1, an authenticated attacker could specify another user's flow ID and execute that flow. The CNA rates the issue 8.4 High, and CISA lists active exploitation.

Why it matters: Langflow Langflow before 1.9.1 can combine untrusted text with connectors, stored credentials, and tool permissions. The meaningful risk is what the surrounding agent is allowed to read, change, or send.

What to verify: Test with hostile input in an isolated environment, inspect connector scopes and retained context, require approval for sensitive actions, and confirm that tool calls are logged and attributable.

CISA remediation date: 2026-07-10. Apply the current Langflow fix and follow CISA KEV remediation guidance.

Operational focus: Inventory tool permissions, connector access, stored credentials, and network reach available to the agent.

Open the original NIST NVD and CISA KEV record

CVE-2026-0770: Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability

CISA Known Exploited Vulnerabilities | July 21, 2026 | Known Exploited | Langflow Langflow

Langflow contains an inclusion of functionality from untrusted control sphere vulnerability that allows remote attackers to execute arbitrary code on affected installations.

Why it matters: Langflow Langflow can combine untrusted text with connectors, stored credentials, and tool permissions. The meaningful risk is what the surrounding agent is allowed to read, change, or send.

What to verify: Test with hostile input in an isolated environment, inspect connector scopes and retained context, require approval for sensitive actions, and confirm that tool calls are logged and attributable.

CISA remediation date: 2026-07-24. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance…

Operational focus: Treat repository text, retrieved documents, web pages, and user prompts as untrusted input.

Open the original CISA Known Exploited Vulnerabilities record

CVE-2026-44101: Due to missing authentication the CHARX OCPP Agent service allows an unauthenticated…

NIST National Vulnerability Database | July 30, 2026 | CRITICAL | CVSS 9.8

Due to missing authentication the CHARX OCPP Agent service allows an unauthenticated remote attacker to reconfigure the backend connection. This can lead to Denial-of-Service and confidential data being disclosed to the attacker.

Why it matters: CVE-2026-44101 should be evaluated as part of the complete model, agent, data, connector, and tool-permission system.

What to verify: Separate confirmed applicability from broad advisory language, assign the remediation decision, and keep any exception visible with an expiry date.

Operational focus: Require approvals and durable logs before an agent changes data or invokes sensitive tools.

Open the original NIST National Vulnerability Database record

Continue reading the full briefing.

Corrections and tips

Need to add context to this briefing?

Send corrections, security tips, source updates, or collaboration notes through the contact page so the editorial team can review them properly.

Contact InfoSecNexus