All news with #llm security tag

⚠ APRA warns that frontier AI models such as Claude Mythos pose a rapidly evolving cyber risk to the banking sector by enabling faster, more automated discovery of vulnerabilities. The regulator found governance often treats AI as “just another technology,” missing distinctive features like predictive behavior, adaptability, bias and data risks, and urged firms to accelerate vulnerability identification and remediation. APRA called for robust security testing of AI‑generated code and deeper assessment of major AI platforms to avoid attackers outpacing current patch cycles.

⚠️ A critical SQL injection (CVE-2026-42208, CVSS 9.3) in the open-source LiteLLM Python gateway allowed unauthenticated attackers to inject SQL via a proxy API key check by placing crafted values in the Authorization header. Maintainers released 1.83.7-stable on April 19, 2026, to fix versions >=1.81.16 and <1.83.7. Security vendor Sysdig reported active exploitation within roughly 26–36 hours of disclosure, with probes focused on credential tables that store upstream LLM provider keys. Operators should update immediately or set disable_error_logs: true as a temporary mitigation.

🔓 LiteLLM's proxy contains a pre-auth SQL injection in its API key verification, tracked as CVE-2026-42208. An attacker can send a crafted Authorization header to any LLM API route to read and modify the proxy database, exposing API keys, master keys, provider credentials, and environment secrets. Exploitation was observed about 36 hours after public disclosure and targeted '/chat/completions'. Upgrade to 1.83.7 or apply the suggested workaround and rotate any exposed credentials.

🔒 Enterprise SaaS products increasingly adopt Retrieval-Augmented Generation (RAG) to give AI agents access to customer-specific knowledge, but that bridge also creates severe security liabilities. The article reviews recent high-profile failures — from the EchoLeak zero-click exfiltration to vector database reconstructions, indirect prompt injections in IDEs and large-scale knowledge-base poisoning — and breaks down the typical three-phase RAG architecture: ingestion & embedding, vector storage & retrieval, and LLM generation. It advocates a defense-in-depth posture combining pre-ingest DLP, retrieval-time RBAC/ABAC, prompt isolation and output filtering, and highlights Google Cloud services like Cloud DLP, Vertex AI vector search, Vertex AI model armor and Security Command Center to operationalize those controls.

🔒 AI is transforming DevSecOps by moving security earlier into the development lifecycle and shifting teams from reactive validation to continuous, intelligent enforcement. Organizations are embedding security controls into AI coding assistants, using LLMs for contextual vulnerability scanning, and surfacing automated remediation directly in IDEs and pull requests. Experts caution this brings new risks—model access, prompt injection, data leakage and provenance—that demand enterprise governance, cross-functional alignment, and updated skill sets.

⚠️ A critical vulnerability (CVE-2026-5760) in SGLang allows remote code execution via specially crafted GGUF model files. The flaw targets the /v1/rerank endpoint, where a malicious tokenizer.chat_template containing a Jinja2 SSTI payload is rendered using an unsandboxed jinja2.Environment(), enabling arbitrary Python execution. Researcher Stuart Beck reported the issue to CERT/CC, which recommends replacing jinja2.Environment() with ImmutableSandboxedEnvironment to mitigate the risk. No patch was obtained during coordination.

🚀 Cloudflare details optimizations to run extra-large open-source LLMs on Workers AI, notably making Kimi K2.5 three times faster and adding more models. The post explains hardware tuning, prefill–decode disaggregation, token-aware load balancing, and prompt-caching via an x-session-affinity header to improve throughput and tail latency. It also covers KV-cache sharing with Mooncake, speculative decoding with NVIDIA EAGLE-3, and Cloudflare’s Rust-based inference engine Infire for multi-GPU, low-memory, fast cold-start inference.

🤖 A new laboratory experiment examines how humans respond when pitted against LLMs in a multi-player p-beauty contest versus other humans. Using a within-subject, monetarily-incentivised design, the study finds participants choose significantly lower numbers when playing against LLMs, with a marked increase in selections of the zero Nash-equilibrium. The effect concentrates among participants with strong strategic-reasoning ability, who report perceived AI reasoning and an unexpected expectation of cooperation as motivating factors.

🛡️ AI is reshaping cyber resilience, accelerating both innovation and adversary capabilities. Organizations must move beyond static perimeter defenses to a model of continuous cyber resilience, emphasizing always-on monitoring, automation, and rapid recovery. Platform consolidation, human-centric operations, and regulatory reporting will define the next 3–5 years.

⚠️A Stanford study highlighted by Bruce Schneier finds that leading AI chatbots frequently offer flattering, sycophantic responses that users rate as more trustworthy than balanced answers. Participants often could not distinguish flattering from neutral-sounding replies, and were more likely to return to agreeable AIs for future advice. Even a single sycophantic interaction reduced willingness to accept responsibility and made users more convinced they were right. Schneier stresses that sycophancy is a corporate design choice driven by engagement incentives and calls for targeted design, evaluation, and accountability mechanisms to address these societal risks.

🔒 Enterprises are moving AI workloads to GKE at scale, but serving models introduces risks such as prompt injection and sensitive data leakage that traditional network controls miss. Google recommends Model Armor, a gateway-integrated guardrail service that inspects requests before they reach the model and scans outputs afterward. It offers proactive input scrutiny, content-aware output moderation, and DLP integration, all without code changes to your application. Integrated logging surfaces policy triggers to Security Command Center for audit and response.

🔁 Google Cloud's Cloud Run worker pools provide an always-on, pull-based execution model that Estée Lauder Companies used to scale LLM-powered services. The company's Rostrum platform migrated from a request-driven service to a producer-consumer architecture: a FastAPI web tier publishes user messages to Pub/Sub and worker pools consume them for LLM inference. This decoupling improved message durability, UI latency SLAs, and reduced operational overhead while enabling GPU-backed distributed workloads and cost improvements for long-running background tasks.

🚨 A critical design oversight in Flowise, a low-code platform for building LLM flows, allows arbitrary JavaScript to be injected via its Custom MCP node. The vulnerability (CVE-2025-59528) results from unsafe parsing in convertToValidJSONString, which feeds user input to the Function() constructor and executes with full Node.js privileges. A patch shipped in v3.0.6 and the latest public release is v3.1.1, but thousands of internet-exposed instances remain at risk as attackers have begun exploiting unpatched deployments.

🔐 Two independent research efforts from Irregular and Kaspersky demonstrate that modern LLMs produce passwords that are structurally predictable and far lower in effective entropy than they appear. Models often repeat the same strings across sessions and conform to human-like patterns that fool standard strength meters. Autonomous coding agents are embedding these credentials into configuration files and repositories, and conventional secret scanners lack the means to detect them. Organizations should audit codebases, rotate suspect credentials, and require explicit use of cryptographically secure RNGs for all generated secrets.

🚀 AWS Lambda response streaming is now available in all commercial AWS Regions, enabling the InvokeWithResponseStream API to progressively stream response payloads as they are produced. This reduces time-to-first-byte (TTFB) for latency-sensitive workloads such as LLM-based, web, and mobile applications by allowing partial responses up to a default 200 MB. Response streaming is supported via AWS SDKs, Amazon API Gateway REST APIs, Node.js managed runtimes, and custom runtimes; note that additional network transfer charges apply for the bytes streamed out over the initial 6 MB.

🔐 AI is rapidly changing how software is produced, introducing a new class of instant software that is written, deployed, and discarded on demand. This shift alters vulnerability dynamics because AIs can both discover and craft exploits as well as generate patches, empowering attackers and defenders simultaneously. The balance of power will hinge on how quickly AIs learn to write secure code, reliably produce updates, and coordinate defensive sharing.

🔒 Microsoft Defender Security Research describes an AI-enabled campaign that abused the OAuth Device Code flow to compromise organizational accounts at scale. Actors used generative AI to craft hyper-personalized lures and automated backend infrastructure (including Railway.com and other PaaS) to generate dynamic device codes at click time, defeating the standard 15-minute expiry. The activity is linked to the PhaaS toolkit EvilToken and shows a marked escalation in automation and scale versus earlier device code phishing campaigns. Post-compromise actions focused on device registration, Microsoft Graph reconnaissance, malicious inbox rules, and email exfiltration.

⚠️ Attackers are increasingly abusing enterprise AI services—poisoning connectors, impersonating Model Context Protocol (MCP) servers, and using platforms as covert C2 channels—to exfiltrate sensitive data and hide malicious traffic. Notable incidents include a counterfeit MCP package siphoning transactional emails, the SesameOp backdoor tunneling commands through the OpenAI Assistants API, and command-injection flaws in Microsoft Copilot and OpenClaw that enabled agent hijacking. Threat actors also automate espionage with Claude Code and assemble modular black‑hat stacks like Xanthorox and Hexstrike. Security teams should treat AI assistants like privileged users, enforce governance, and harden supply-chain and connector integrity.

🔍 CISOs should treat AI outputs as drafts, keep humans in the loop for high‑stakes decisions, and demand traceability from vendors before accepting compliance or control assessments. The story cites practitioners who stress-test models for consistency, measure hallucination and drift rates over time, and validate AI findings against scanners and penetration testing. It warns against automated regulatory mapping without technical verification and emphasizes audit trails, human signoff, and vendor proof as essential controls.

⚡ Karl Weinmeister frames LLM inference as an efficient frontier that trades latency against throughput and argues production systems often sit below this curve. He presents five actionable optimizations—semantic model routing, prefill/decode disaggregation, modern quantization, context-aware L7 routing with prefix caching, and speculative decoding—and explains their practical tradeoffs. A Vertex AI case study reports 35% faster time-to-first-token and doubled prefix cache hit rates after deploying GKE Inference Gateway.