All tracked items across vulnerabilities, news, research, incidents, and regulatory updates.
Gushwork, an India-founded startup, is helping businesses get discovered through AI-powered search tools (systems like ChatGPT and Perplexity that use artificial intelligence to answer questions) by automatically creating search-optimized content and building backlinks (links from other websites that point to a business's site). The company raised $9 million in funding and reports that AI-driven search and chat platforms now account for about 40% of inbound leads for its customers, despite representing only 20% of website traffic.
A Chinese internet activist accidentally exposed details about coordinated political influence operations (organized campaigns to manipulate public opinion) that used ChatGPT to create negative content about Japan's Prime Minister Takaichi. The leak revealed how ChatGPT was being used as a tool to generate misleading material for political purposes.
Anthropic acquired Vercept, an AI startup that built tools for agentic tasks (AI systems that can independently perform complex actions), including a product called Vy that could control remote computers. Vercept's product will shut down on March 25, with some co-founders joining Anthropic while others, including investor Oren Etzioni, expressed disappointment about the acquisition ending the startup after just over a year.
Alphabet is folding its robotics software company Intrinsic into Google to streamline its business. Intrinsic developed Flowstate, a web-based platform that lets users build robotic applications without writing thousands of lines of code, addressing the challenge that programming robots remains extremely complex despite hardware becoming cheaper. By joining Google, Intrinsic will use Google's AI models and infrastructure to expand its industrial robotics platform for manufacturing and logistics.
LangGraph versions before 4.0.0 have a remote code execution vulnerability in their caching layer when applications enable cache backends and opt nodes into caching. The vulnerability occurs because the default serializer uses pickle deserialization (a Python feature that can execute arbitrary code) as a fallback when other serialization methods fail, allowing attackers who can write to the cache to execute malicious code.
The zae-limiter library has a security flaw where all rate limit buckets for a single user share the same DynamoDB partition key (the identifier that determines which storage location holds the data), allowing a high-traffic user to exceed DynamoDB's write limits and cause service slowdowns for that user and potentially others sharing the same partition. This vulnerability affects multi-tenant systems, like shared LLM proxies (AI services shared across multiple customers), where one customer's heavy traffic can degrade service for others.
n8n, a workflow automation platform, has a stored XSS (cross-site scripting, where attackers inject malicious code into a website that runs when other users visit it) vulnerability in multiple nodes. An authenticated user with workflow creation permissions could inject malicious scripts that execute in other users' browsers, potentially leading to session hijacking (stealing a user's active login) and account takeover.
n8n, a workflow automation tool, has a vulnerability where authenticated users with permission to create or modify workflows can exploit expression evaluation (the process of interpreting code within workflow parameters) to execute arbitrary system commands on the host server. This is a serious security flaw because it allows attackers to run unintended commands on the underlying system.
Flaws have been discovered in Claude (an AI assistant) that can put developers' computers at risk when Claude is used in software development workflows. These vulnerabilities could potentially affect supply chains, which are the networks of companies and systems that work together to deliver software and products.
n8n (a workflow automation tool) has a vulnerability where an authenticated user with workflow editing permissions could combine the Read/Write Files from Disk node (a component that modifies files on the server) with git operations (version control commands) to execute arbitrary shell commands (any commands an attacker chooses) on the n8n server. This requires the attacker to already have valid user access.
n8n, a workflow automation tool, has a vulnerability where authenticated users with workflow editing permissions could use the Merge node's SQL query mode to execute arbitrary code (running any commands they want on the server) and write files to the n8n server. This is a serious security issue because it lets trusted insiders cause significant damage.
n8n, a workflow automation tool, has a sandbox escape vulnerability in its JavaScript Task Runner that lets authenticated users run code outside the sandbox (a restricted environment for running untrusted code). On default setups, this could give attackers full control of the n8n server, while on systems using external task runners, attackers could impact other workflows.
n8n, a workflow automation platform, has a vulnerability where authenticated users with permission to create workflows could escape the sandbox (an isolated environment that restricts what code can do) in the Python Code node to read arbitrary files or achieve RCE (remote code execution, where an attacker can run commands on a system they don't own). On default setups, this could compromise the entire n8n host machine.
n8n had a vulnerability in its Form nodes where an unauthenticated attacker could inject malicious code by submitting specially crafted form data that starts with an equals sign (=), which the system would then execute as an expression. While this vulnerability alone is limited, it could potentially lead to remote code execution if combined with another type of attack that bypasses n8n's expression sandbox (a security boundary that restricts what code can access).
President Trump announced plans for major tech companies to sign a 'rate payer protection pledge' that would require them to build or pay for new electricity generation for their data centers, aiming to reduce concerns about rising electricity costs. Leaders from Amazon, Google, Meta, Microsoft, xAI, Oracle, and OpenAI are expected to attend a signing event on March 4th, though details about the pledge's requirements and enforcement mechanisms remain unclear.
Google and Samsung announced that Gemini, Google's AI assistant, will soon handle multi-step tasks on phones like ordering food or booking rides, starting with Pixel 10 and Galaxy S26 phones. This represents agentic AI features (AI that can take multiple actions toward a goal) that Apple had planned for Siri but delayed in March 2025 and hasn't yet released.
Thrive Capital, a venture capital firm (a company that invests in startups), invested about $1 billion in OpenAI at a $285 billion valuation in December 2024. OpenAI is currently finalizing a much larger funding round that could total over $100 billion and raise the company's valuation to $800 billion, with Thrive likely participating in this round as well.
Samsung's Galaxy S26 smartphone combines three AI assistants: Google's Gemini (which can now perform autonomous actions inside third-party apps), Perplexity for web searches, and an upgraded Samsung Bixby for on-device tasks. This multi-agent approach (using multiple separate AI systems together) gives Google's Gemini major market reach before Apple launches a Gemini-powered version of Siri later in 2025, with features that were originally planned for March or April now delayed to May or September.
Parse Dashboard has a cache key collision bug where the same storage identifier is used for both the master key (full access) and read-only master key (limited access) when resolving function-typed keys. Under specific timing conditions, a read-only user could receive the full master key, or a regular user could receive the read-only master key, leaking access privileges to the wrong user type.
LangChain's `RecursiveUrlLoader` component had a security flaw where it would validate an initial website address but then automatically follow redirects (automatic jumps to different URLs) without checking them, allowing attackers to redirect from a safe public URL to internal or sensitive endpoints. This vulnerability was fixed in version 1.1.18 of the `@langchain/community` package.
Fix: Upgrade to langgraph-checkpoint>=4.0.0, which disables pickle fallback by default (pickle_fallback=False).
GitHub Advisory DatabaseFix: The source explicitly describes a remediation design called 'Pre-Shard Buckets' that includes: moving buckets to a new partition key format with sharding (`PK={ns}/BUCKET#{entity}#{resource}#{shard}, SK=#STATE`), auto-injecting a `wcu:1000` reserved limit on every bucket to track DynamoDB write pressure, implementing shard doubling (1→2→4→8) when capacity is exhausted, storing original limits on the bucket with effective limits derived by dividing by shard count, using random or round-robin shard selection with retry logic (maximum 2 retries), lazy shard creation on first access, discovering shards via GSI3 (a secondary index), and implementing a clean break migration with a schema version bump so old buckets are ignored and new buckets are created on first access.
GitHub Advisory DatabaseFix: The issues have been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can temporarily limit workflow creation and editing permissions to fully trusted users only, or disable the Webhook node by adding 'n8n-nodes-base.webhook' to the 'NODES_EXCLUDE' environment variable. However, these workarounds do not fully remediate the risk and should only be used as short-term measures.
GitHub Advisory DatabaseFix: Upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not possible, limit workflow creation and editing permissions to fully trusted users only, and deploy n8n in a hardened environment with restricted operating system privileges and network access. However, these temporary mitigations do not fully remediate the risk.
GitHub Advisory DatabaseFix: The issue has been fixed in n8n versions 2.2.0 and 1.123.8. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can temporarily: (1) Limit workflow creation and editing permissions to fully trusted users only, or (2) Disable the Read/Write Files from Disk node by adding `n8n-nodes-base.readWriteFile` to the `NODES_EXCLUDE` environment variable. The source notes these workarounds do not fully remediate the risk and should only be short-term measures.
GitHub Advisory DatabaseFix: The vulnerability is fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22 or later. If upgrading immediately is not possible, administrators can temporarily restrict workflow creation and editing permissions to only fully trusted users, or disable the Merge node by adding `n8n-nodes-base.merge` to the `NODES_EXCLUDE` environment variable (a configuration setting that tells n8n which features to turn off). Note: these workarounds do not fully eliminate the risk and are only short-term measures.
GitHub Advisory DatabaseFix: Upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22 or later. If immediate upgrade is not possible, temporarily limit workflow creation and editing permissions to trusted users only, or use external runner mode by setting N8N_RUNNERS_MODE=external to reduce potential damage.
GitHub Advisory DatabaseFix: The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can: (1) Limit workflow creation and editing permissions to fully trusted users only, or (2) Disable the Code node by adding `n8n-nodes-base.code` to the `NODES_EXCLUDE` environment variable. The source notes these workarounds do not fully remediate the risk and should only be used as short-term measures.
GitHub Advisory DatabaseFix: The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to one of these versions or later. If upgrading is not immediately possible, administrators can temporarily: (1) manually review form nodes to check if they have the problematic configuration, (2) disable the Form node by adding `n8n-nodes-base.form` to the `NODES_EXCLUDE` environment variable, or (3) disable the Form Trigger node by adding `n8n-nodes-base.formTrigger` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term measures.
GitHub Advisory DatabaseFix: The patch uses distinct cache keys for master key and read-only master key. As workarounds, avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration. This issue is fixed in version 9.0.0-alpha.8 or later.
GitHub Advisory DatabaseFix: Upgrade to `@langchain/community` version 1.1.18. This version disables automatic redirects (`redirect: "manual"`), validates each redirect target with `validateSafeUrl()` before following it, and implements a maximum redirect limit to prevent infinite loops.
NVD/CVE Database