Mage AI at 1,207 application matches: the pipeline UI holds connection and trigger authority
Mage AI is a self-hosted data-pipeline environment. Its interface lets users build pipelines, write code blocks, schedule runs, and connect to databases, APIs, cloud storage, and other services. The UI and API are therefore part of the data control plane. A public Mage endpoint can expose pipeline definitions, run history, model credentials, and the ability to execute code.
ZoomEye returned 21 matches for title="Mage AI" and 1,207 for app="Mage AI" on November 18, 2026, using sub_type=all, page 1, and page size 1. The application fingerprint is the more specific observation. It still does not prove that 1,207 deployments are misconfigured, vulnerable, or even reachable after the scan. It indicates that the application classification is much more common than the exact title tag.
Mage's open-source documentation describes the application as a self-hosted development environment at port 6789 with a REST API for pipelines, blocks, schedules, and triggers. The project's container configuration includes REQUIRE_USER_AUTHENTICATION, which controls whether the user interface requires authentication. The API reference describes pipeline and trigger endpoints that can create and run work.
A pipeline is a place to put secrets
A data pipeline often contains database URLs, warehouse credentials, cloud storage keys, model API keys, and connection settings. A user who can edit a pipeline may be able to execute arbitrary Python in a block. A user who can trigger a pipeline can cause it to use the credentials attached to the project. A user who can change a schedule can make that execution repeat.
The authentication setting is only the first layer. If REQUIRE_USER_AUTHENTICATION is false, the interface may be reachable without a login. If it is true, the application still needs a role model for who can edit, run, and publish a pipeline. Review the front-end login and the API separately. A UI that hides the run button does not prove that the /api route rejects an unauthenticated trigger request.
Connection credentials should be scoped to the pipeline and environment. A development pipeline that reads sample data should not use the production warehouse administrator. A scheduled pipeline should use a dedicated service account with a documented owner. Rotate credentials when a pipeline is copied, archived, or moved between environments.
What to inventory
List every Mage instance by environment, project, owner, and exposure path. Determine whether it is an open-source development instance or a managed/pro deployment. Check the authentication mode and the project members. Review API keys and OAuth tokens, scheduled triggers, webhook endpoints, and recent run history.
Test a low-privilege account against pipeline creation, block editing, trigger creation, and execution. Confirm that a user cannot read another project's connections or run history. If the instance uses a shared account, replace it with individual identities before relying on audit logs. A shared login turns every change into an anonymous administrative event.
For external exposure, remove public access unless there is a deliberate use case. Put the UI and API behind a private network or a strong identity-aware proxy. Restrict the application's egress to the databases and APIs it needs. Block access to cloud metadata endpoints and internal management planes from pipeline containers. Use a separate runner or network namespace for untrusted code where the product supports it.
Mage's application count is useful because it shows how often a common pipeline product can be identified even when the title is custom. It is not a count of vulnerable servers. The more important question is whether the identified instance can execute a pipeline and whether that pipeline can reach data or credentials that the visitor should not control.
Query evidence
app="Mage AI" sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:41:34+08:00, count=1,207 title="Mage AI" sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:41:33+08:00, count=21