
What happened
VicOne identified 28 zero-day findings in under two days using AI-assisted research across software from Google, NVIDIA, and Meta. All 28 are classified as zero-day vulnerabilities, though some lack CVE tracking numbers.
Why it matters
These weaknesses sit in tools teams use to train, simulate, test, and operate robots, so they could affect the models built, the test results trusted, and the instructions sent to robots.
WHO IT HITSRobotics engineering and security teams that rely on development, simulation, and runtime tools from major vendors may need to check whether affected software is in their stack and whether existing safeguards still hold.
Summaries like this, every morning.
VicOne's disclosure arrives as AI tools are changing how quickly software weaknesses can be found. The company says AI can accelerate parts of vulnerability discovery, letting researchers analyze more software in less time, and that attackers could use similar capabilities. When the weakness is a zero-day — previously unknown and without an available fix — that speed can leave teams with little time to respond.
The 28 findings span three stages of the robotics lifecycle: development and training, simulation and validation, and deployment and runtime. In this research set, 75% of findings involved development, training, simulation, or validation tools, highlighting risks that can arise before a robot is deployed. VicOne outlines scenarios where a compromised component could influence the robot at each stage, such as a manipulated model behaving normally during routine testing but responding incorrectly after deployment, or altered simulated sensor readings leading a robot to appear to pass tests that should have exposed unsafe behavior.
VicOne notes that these are potential consequences and not demonstrated outcomes for every finding, with actual effects depending on the attacker's access, the system's design, and whether other safeguards prevent the changes from reaching physical behavior. In a separate demonstration, VicOne researchers showed a vulnerability that prevented a robot's remote-stop command from working, illustrating why teams need to test whether safeguards remain effective when supporting software is compromised. As details become available through coordinated disclosure, the next step for robotics manufacturers is to connect each finding to its potential effect on development, deployment, and robot behavior.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Robotics and physical AI startups raised a record $27.6 billion across 1,009 deals in 2025, more than double t…

In 100 sessions using the GAD-7 anxiety questionnaire, 80% of sessions scored moderate-to-severe under a suppo…

Anthropic is reportedly asking candidates how they would feel if it abandoned AI ambitions for safety and its…

OpenAI's Misalignment Reports, launched September 16, 2026, list 20 reports as of October 30

Parameter reported on October 18 that a crafted ChatGPT share link could execute code in a victim's signed-in…

Three 20-year-olds on Mount Shasta relied partly on Google's Gemini for planning, summited at 7:30 pm, got los…
