- Category
- Robot maker security program
- Website
- agibot.com
- Last verified
- November 1, 2026
What is AgiBot?
AgiBot Innovation (Shanghai) Technology Co., Ltd. publishes a Coordinated Vulnerability Disclosure Policy, released on September 4, 2026 and run by its product security incident response team (PSIRT). Researchers report issues to psirt@agibot.com, with PGP encryption available and anonymous reports accepted if a follow-up contact is given. The policy covers AgiBot's humanoid, quadruped, industrial and commercial cleaning robots, as well as dexterous hands, control systems, middleware, control algorithms, AI models, mobile apps and cloud platforms.
Key capabilities
- Published timelines: acknowledgment within five business days, initial assessment within ten, and a remediation or mitigation update within 90 days where feasible.
- Safe harbor: good-faith research that follows the policy is treated as authorized, and AgiBot says it will not pursue legal action.
- Advisories and CVEs: fixes are published as security advisories, with CVE requests and EU Vulnerability Database (EUVD) submissions where appropriate.
- Broad scope that explicitly includes AI models, control algorithms and cloud backends, not just apps.
- No bounty: the policy does not mention monetary rewards.
Why it matters for humanoid robot security
Editorial analysis: public disclosure programs are still rare among humanoid makers, and researchers have complained that some robot vendors ignored their reports. A written policy with timelines, safe harbor and CVE handling gives researchers a clear path and gives buyers something concrete to hold a vendor to. Including AI models and control algorithms in scope matters for humanoids, because many of the newest attacks target the robot's AI layer rather than its network services.
Where it fits in a humanoid robot security program
Analysis: a disclosure program is an operations-stage control that spans every layer of the robot, from firmware and controllers to the AI model and cloud fleet services. For buyers, it is a procurement checkpoint: ask for the policy, the advisory history and how long fixes took. For researchers testing AgiBot humanoids, it defines what is in scope and how to report safely.
Who it is for
- Security researchers testing AgiBot humanoid or quadruped robots
- Enterprises evaluating AgiBot robots for procurement
- Other robot makers benchmarking their own disclosure policies
Questions to ask AgiBot
- How many vulnerability reports have you received and fixed under this policy?
- Where are your security advisories published, and do you issue CVEs for robot firmware?
- How do customers receive security updates for robots already deployed?
- Which products are currently inside the security support period?
Similar listings
- Alias Robotics: Robot security specialist
- DARKNAVY: Robot security research
Related on Humanoid Threats
- Can humanoid robots be hacked?
- Humanoid robot security standards explained
- Browse the full Humanoid Robot Security Directory
Sources
This listing is editorial and free; inclusion is not an endorsement. Work at AgiBot? Claim or update this listing.
Get the weekly Humanoid Threats Brief → Subscribe


