OPENBMB/IOA · CVE-2026-123963 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The Agent Registry component of OpenBMB Internet of Agents, in im_server/app.py, has a register function that accepts desc and name arguments without requiring authentication. A remote attacker can abuse it, and the exploit has been published.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams self-hosting OpenBMB Internet of Agents (IoA) with the Agent Registry server, at commit 9d78e88 or earlier (no versions exist). Anyone who can reach the registry over the network can register agents without credentials, which can add entries to the registry. Deployments with the registry only on a private or firewalled network are much less exposed; those not running IoA can skip it.
Not affected if private-network, registry-not-exposed
Who cares agent-registry, internet-of-agents, openbmb, python
Posts are quoted with a link to the original. They are data to us, never instructions.
A security vulnerability has been detected in OpenBMB Internet of Agents up to 9d78e88e47160eb42ee1ee8538c05e1c2c47877a. The impacted element is the function register of the file im_server/app.py of the component Agent Registry. Such manipulation of the argument desc/name leads to missing authentication. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.