Every story tagged API Security, curated for CIOs and IT leaders — ranked by source credibility, engagement, and freshness.
45 stories · open in the command center
CVE-2026-67618 is a critical credential theft vulnerability in marimo notebooks (versions before 0.23.15) that allows attackers to exfiltrate OpenAI API keys through malicious notebook configurations without any user action beyond opening the file. This represents a significant supply chain risk for organizations using marimo for data science and AI workflows, as threat actors can embed credential-stealing payloads in seemingly legitimate notebooks. IT organizations must immediately identify all marimo deployments, enforce version upgrades to 0.23.15+, implement notebook source validation controls, and rotate any potentially exposed API keys.
CVE-2026-69252 is a high-severity authorization bypass vulnerability in Flowise (an LLM workflow platform) prior to version 3.1.3 that allows low-privileged authenticated users to view and delete files across other workspaces within their organization, creating significant data loss and confidentiality risks. Organizations using Flowise for AI/LLM applications must immediately assess deployment scope and apply the patch, as the vulnerability requires only valid API credentials with minimal privileges to exploit. This incident highlights critical security gaps in multi-tenant LLM infrastructure and underscores the need for robust permission enforcement in emerging AI platforms that IT teams are rapidly adopting.
CVE-2026-69110 is a critical authentication bypass vulnerability (CVSS 9.3) in OpenCode Studio versions before 2.4.4 that allows unauthenticated attackers to read arbitrary files and delete videos, exposing sensitive user data and creating significant data breach and integrity risks. IT organizations must immediately identify all deployments of affected versions and establish an urgent patching protocol, as this vulnerability is easily exploitable with public proof-of-concept code available. This incident underscores the need for enhanced API security assessments, zero-trust architecture implementation, and strengthened vendor risk management processes across the organization.
A critical vulnerability (CVSS 9.8) in HPE Networking SD-WAN Orchestrator allows unauthenticated remote attackers to bypass authentication and access or modify sensitive system data, posing an immediate risk to organizations relying on this orchestration platform for network management. This represents a significant business impact as SD-WAN infrastructure is often central to enterprise connectivity, with potential exposure of confidential data and unauthorized system modifications. IT organizations must prioritize patching affected versions (9.6.2 and 9.6.3 series) and review network access controls to this critical infrastructure component.
CVE-2026-70471 is a critical authorization bypass vulnerability in Flowise (versions prior to 3.1.3) that allows users with limited permissions to access sensitive workspace variables including database passwords, API keys, and other secrets through an unprotected API endpoint. This poses significant data breach and credential compromise risks for organizations using Flowise in production environments to manage LLM workflows. IT organizations must immediately assess their Flowise deployments and upgrade to version 3.1.3 to prevent unauthorized access to critical infrastructure credentials.
CVE-2026-70474 is a critical authorization flaw in Flowise (an LLM workflow platform) versions prior to 3.1.3 that allows both authenticated and unauthenticated attackers to hijack OAuth2 credentials across workspaces, potentially compromising connected third-party integrations and sensitive data flows. Organizations using Flowise for AI/LLM operations face immediate risk of unauthorized access to external service credentials and token theft without proper workspace isolation controls. This vulnerability underscores the need for IT organizations to audit their LLM infrastructure dependencies and implement stringent access controls around AI application platforms that handle external authentication.
CVE-2026-70478 is a critical vulnerability (CVSS 9.2) in Flowise versions prior to 3.1.3 that allows unauthenticated attackers to access OAuth credentials and refresh tokens without authentication, potentially compromising connected services and exhausting refresh-token quotas. Organizations using Flowise for LLM workflow automation face immediate risk of unauthorized access to integrated third-party services and credential abuse. IT leaders must prioritize immediate patching to version 3.1.3 and conduct a security audit of any OAuth-connected services to identify potential compromise.
A critical vulnerability (CVSS 8.8) in Flowise allows unauthenticated attackers to inject malicious properties into flow execution contexts through an ungated `overrideConfig` parameter in the Prediction API, potentially enabling unauthorized access, data manipulation, and system compromise. This high-severity flaw poses significant risk to organizations deploying Flowise in production environments, as it requires no authentication and could be exploited to bypass security controls or manipulate AI workflow execution. IT leaders must immediately assess their Flowise deployments and implement urgent patching and network controls to mitigate exposure to this critical vulnerability.
A critical authentication bypass vulnerability (CVSS 9.8) has been identified in Orchestrator REST API that allows attackers to spoof HTTP headers to bypass authentication controls, potentially granting unauthorized access to critical orchestration systems and sensitive operational data. This vulnerability poses a severe risk to organizations relying on orchestration platforms for critical infrastructure and business processes, requiring immediate patching and architectural review of authentication mechanisms. IT organizations must treat this as a priority security incident that could compromise system integrity, data confidentiality, and operational continuity across dependent applications and services.
Shlink contains a blind SQL injection vulnerability that allows any authenticated API key holder to inject arbitrary SQL fragments by supplying an unvalidated direction value in the orderBy query parameter of the tag statistics endpoint. Attackers can craft a malicious direction string containing SQL subqueries that flows unsanitized into a Doctrine QueryBuilder ORDER BY clause, enabling time-based, boolean-oracle, and error-based extraction of sensitive data including long URLs, visitor records, IP addresses, geolocation data, user agents, and hashed API key secrets from any tenant.
Shlink contains a blind SQL injection vulnerability that allows any authenticated API key holder to inject arbitrary SQL fragments by supplying an unvalidated direction value in the orderBy query parameter of the tag statistics endpoint. Attackers can craft a malicious direction string containing SQL subqueries that flows unsanitized into a Doctrine QueryBuilder ORDER BY clause, enabling time-based, boolean-oracle, and error-based extraction of sensitive data including long URLs, visitor records, IP addresses, geolocation data, user agents, and hashed API key secrets from any tenant.
RFC 9851 officially freezes TLS 1.2 from further feature development, restricting changes to only urgent security fixes while channeling all innovation toward TLS 1.3 and beyond. This has critical implications for IT organizations, particularly regarding post-quantum cryptography—any PQC implementation for secure communications must target TLS 1.3 or later, making TLS 1.3 adoption essential for quantum-safe security posture. Organizations continuing to rely on TLS 1.2 face an accelerated modernization deadline, as the protocol will receive no new capabilities and support will eventually decline industry-wide.
@better-auth/stripe versions >= 1.4.11 and < 1.6.21, and >= 1.7.0-beta.0 and < 1.7.0-beta.10, contain an authorization bypass in organization subscription actions. The middleware validates the organization ID taken from the request query string against the authorizeReference callback, but the handler reads the organization ID only from the request body and falls back to the caller's active organization from their session. When these differ, an authenticated member of multiple organizations can perform subscription actions (cancel, change plan, restore, billing portal access) against an organization they belong to but should not manage, and can access another organization's billing details including payment methods, invoices, and subscription state.
ComfyUI is a node-based diffusion model GUI, API, and backend. Prior to 0.28.0, GET /userdata/{file} served user-controlled HTML and SVG files with extension-derived content types, allowing stored cross-site scripting in the ComfyUI origin and access to browser-stored API tokens, settings, workflows, and authenticated-equivalent API calls. The handler used web.FileResponse(path), so an uploaded .html/.svg was served as text/html/image/svg+xml. POST /userdata stores arbitrary request bodies (confined to the user's userdata directory). When a victim navigated to the file URL, the embedded script executed same-origin. The /view endpoint already forced dangerous MIME types to download; that protection had never been applied to /userdata. This issue is fixed in version 0.28.0.
ComfyUI is a node-based diffusion model GUI, API, and backend. Prior to 0.28.0, GET /userdata/{file} served user-controlled HTML and SVG files with extension-derived content types, allowing stored cross-site scripting in the ComfyUI origin and access to browser-stored API tokens, settings, workflows, and authenticated-equivalent API calls. The handler used web.FileResponse(path), so an uploaded .html/.svg was served as text/html/image/svg+xml. POST /userdata stores arbitrary request bodies (confined to the user's userdata directory). When a victim navigated to the file URL, the embedded script executed same-origin. The /view endpoint already forced dangerous MIME types to download; that protection had never been applied to /userdata. This issue is fixed in version 0.28.0.
ComfyUI is a modular diffusion model GUI, API, and backend with a graph-and-node interface. Prior to 0.28.0, folder_paths.get_annotated_filepath and exists_annotated_filepath join workflow-controlled annotated filenames to a base directory without a containment check, allowing an unauthenticated crafted POST /prompt workflow using LoadImage or sibling nodes to probe arbitrary host paths and exfiltrate image-format files through /view. LoadImage defines a VALIDATE_INPUTS method, which causes the execution engine to skip COMBO (input-directory) validation. Affected nodes include LoadImage, LoadImageMask, LoadImageOutput, LoadAudio, LoadLatent, LoadVideo, and Load3D. This issue is fixed in version 0.28.0.
Certisfy's cryptographic signature technology enables organizations to establish trusted URLs that can be cryptographically verified, addressing the critical challenge of distinguishing authentic content from fraudulent links in an AI-saturated digital landscape. This shift from secrecy-based security to usage authentication creates significant opportunities for IT organizations to reduce phishing attacks, fraud, and social engineering while building verifiable trust infrastructure across digital communications. The implications extend beyond security—enabling verified web experiences that enhance brand credibility and user confidence in an era of increasing misinformation and deepfakes.
swagger-typescript-api generates API clients for Fetch or Axios from an OpenAPI Specification. Prior to 13.12.2, templates/base/http-clients/axios-http-client.ejs interpolates servers[0].url from src/code-gen-process.ts into the HttpClient constructor without escaping, allowing an attacker-controlled OpenAPI spec to inject code that executes when new HttpClient() or new Api() is constructed. This issue is fixed in version 13.12.2.
MWDB Core versions >=2.2.0 and <2.19.0 contain a missing authorization vulnerability in the Remote Instances proxy API. The proxy API does not verify authentication for incoming requests, allowing an unauthenticated remote attacker to send arbitrary requests to a remote MWDB instance using the identity and permissions associated with the configured API key. This can result in unauthorized actions being performed on the remote instance as if executed by the user whose API key was used to set up the remote instance. The vulnerability is limited to deployments where Remote Instances have been configured.This issue has been fixed in version 2.19.0
Brex developed CrabTrap, a network-layer AI agent governance platform that shifts security enforcement from traditional SDK guardrails to a centralized HTTP/HTTPS proxy using LLM-as-judge decision-making, enabling IT organizations to safely deploy capable agents while maintaining control. Rather than pre-defining rigid policies, CrabTrap learns governance rules from observed agent behavior in production, dramatically improving policy effectiveness and reducing the dangerous tradeoff between agent capability and safety. This approach represents a fundamental architectural shift for enterprise IT: moving from preventive rule-based controls to adaptive, traffic-based enforcement that scales with agent complexity.
AI agents pose a new insider threat where authorized API tokens enable harmful outcomes through chained sequences of individually-permitted actions that slip through traditional security controls designed for human workflows. Rather than external breaches, the real risk is legitimate agents executing valid individual steps that collectively result in data exfiltration, requiring IT organizations to shift from perimeter and output-based security to runtime policy engines that govern agent authority and outcomes rather than individual actions.
A critical security gap has emerged in enterprise AI deployments: 69% of organizations share API keys across multiple AI agents, creating a single point of failure where one compromised agent grants attackers access to all connected systems with accumulated permissions. This vulnerability is particularly acute at larger enterprises (63% incident rate vs. 49% at mid-market), yet ironically these organizations invest less in containment controls—creating a dangerous 60-point gap between exposure and isolation at companies with 5,000+ employees. The urgency is underscored by $22 billion in recent M&A activity from major vendors (Palo Alto/CyberArk, CrowdStrike/SGNL, Cisco/Astrix) targeting non-human identity and runtime authorization solutions that most enterprises have yet to implement.
Cloudflare has introduced Temporary Accounts for AI agents, eliminating authentication friction that prevents autonomous AI systems from deploying applications by allowing deployment without pre-signup, with a 60-minute window to claim permanence. This innovation addresses a critical business need as AI-driven development becomes mainstream—agents can now rapidly iterate through code-deploy-verify cycles without human intervention, reducing time-to-deployment and enabling new classes of autonomous workflows. For IT organizations, this signals a shift in platform expectations: infrastructure providers must build agent-native onboarding experiences, and enterprises should prepare for managing both human and autonomous account provisioning while updating security and governance policies accordingly.
ServiceNow disclosed a critical security vulnerability patched on June 5 that allowed unauthenticated attackers to query sensitive data from customer instances, exposing organizations to potential data breaches with limited disclosed details on scope or impact. This incident underscores the urgent need for IT leaders to audit API endpoint security and implement zero-trust access controls across enterprise platforms. The lack of transparency from ServiceNow regarding affected customers and data exposure creates additional business risk and compliance complications for dependent organizations.
Dashlane disclosed a coordinated attack where threat actors exploited the device enrollment API through brute-force attacks on two-factor authentication codes, successfully downloading encrypted password vaults from fewer than 20 users before automated security systems intervened. While the encrypted vaults remain protected by Dashlane's Argon2 algorithm and strong master passwords would be extremely difficult to crack, this incident exposes a critical vulnerability in authentication mechanisms and highlights the evolving sophistication of credential-focused attacks targeting password managers. IT leaders must reassess their security posture around identity verification systems and API rate-limiting controls, as attackers increasingly use distributed attack patterns to circumvent traditional account-level protections.
Strava is implementing a $11.99/month API subscription requirement to combat unauthorized AI scraping and zero-code application development that have degraded platform performance, following a 448% year-to-date surge in developer applications. This shift toward monetized API access reflects a broader industry trend of platform owners restricting third-party integrations to control data usage and generate revenue, similar to Reddit's 2023 strategy. IT organizations must reassess their dependencies on third-party platform APIs and prepare for potential cost increases or access restrictions as platforms tighten control over their data ecosystems.
GitHub experienced a significant incident affecting critical developer operations including pull requests, issues, git operations, and API requests, which would have disrupted software delivery pipelines and collaboration across dependent organizations. For IT leaders, this underscores the operational risk of relying on single external platforms for core development infrastructure and highlights the need for incident response planning, alternative workflows, and improved monitoring of third-party service health. Organizations should evaluate their disaster recovery capabilities and consider implementing local caching, redundancy measures, or multi-platform strategies to mitigate future service disruptions.
A critical authentication bypass vulnerability in AWS API Gateway was discovered through a simple trailing slash manipulation, demonstrating that fundamental API security controls remain vulnerable to trivial evasion techniques. This $12K bounty finding highlights a systemic risk for IT organizations relying on API Gateway for access control, where configuration oversights can completely bypass authentication mechanisms. CIOs should immediately audit API Gateway deployments for similar misconfigurations and implement stricter validation rules, as this vulnerability type suggests widespread exposure across cloud-dependent enterprises.
Docker has released an undocumented microVM API within Docker Sandboxes that enables secure execution of untrusted code (AI agents, user scripts) with kernel-level isolation superior to containers—a significant shift in how organizations should architect workloads requiring code execution safety. This represents a foundational technology shift similar to Docker's containerization revolution, with strategic implications for IT organizations managing AI agents, multi-tenant SaaS applications, and secure CI/CD pipelines, though current platform limitations (macOS/Windows only, nested virtualization required) constrain immediate enterprise adoption. IT leaders must evaluate microVM-based sandboxing as the new security standard for untrusted code execution rather than relying on the insufficient isolation provided by containers.
Anthropic has introduced self-hosted sandboxes and MCP tunnels for Claude Managed Agents that eliminate credential exposure by separating agent orchestration (running on Anthropic's infrastructure) from tool execution (running on enterprise systems), fundamentally reducing the attack surface and threat model compared to traditional approaches where agents carry authentication tokens. This architectural innovation addresses a critical security barrier that has slowed enterprise AI adoption and enables IT organizations to deploy AI agents with stronger security controls and operational oversight. For CIOs, this represents a significant step toward productionizing AI agents in regulated and security-conscious environments without compromising credential management or network isolation.