Port 1862MySQL Cluster Manager Agent

Port 1862 is assigned to the MySQL Cluster Manager Agent for MySQL Cluster Manager deployments.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 7/10
lookups: 0

also known as mysql-cm-agent

Technical Details

what runs on :1862

The default MySQL Cluster Manager agent port is TCP 1862. The agent accepts proprietary management-protocol connections from the MCM management client and other cluster-management components; the protocol is not the MySQL client/server wire protocol, and UDP is not normally expected in a standard MCM deployment despite the IANA registration covering both transports. The service's management functions include coordinating cluster process startup, shutdown, and configuration, while the NDB data nodes and MySQL SQL nodes use their own ports.

Security Information

exposure of :1862

risk score

7/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

databases averages 3.9 across 135 ports — this one sits 3.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

This is a remote administration interface, not a port that should be exposed to the public Internet. Restrict it to trusted management hosts with firewall rules, require authentication, and use the product's TLS or an authenticated tunnel where supported; an exposed or weakly protected agent could permit disruptive changes to cluster services and configuration.

Record

iana registry entry

port: :1862
service: MySQL Cluster Manager Agent
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 7/10risk
category: Databases
usage: MySQL Cluster Manager agents listen here on hosts managed by MySQL Cluster Manager, allowing the management client to administer MySQL NDB Cluster processes and configuration. It is normally encountered inside a private cluster-management network rather than as a public database listener.
lookups: 0rank 993
added: 2026-08-22
updated: 2026-09-22
references: IANA service name registry — port 1862

Something wrong?

This record is maintained by the engineers who use port 1862. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-09-22.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

all 135 in databases →

the 8 most looked-up other ports in databases — 135 ports carry that label.

port	service	proto	category	risk	views
:8882	Atlasz Secure App Server	TCP	Web Services	caution	66.9k
:9001	ETL Service Manager	TCPUDP	Databases	caution	28.6k
:2484	Oracle SSL Listener	TCPUDPtls	Security	caution	25.0k
:5495	Applix TM1 Admin	TCP	Databases	caution	24.8k
:591	FileMaker Web Sharing	TCP	Web Services	caution	23.1k
:1521	Oracle TNS Listener	TCP	Security	caution	19.6k
:21001	AMLFilter Admin	TCP	Security	caution	19.2k
:18206	Audition FAM DB	TCPUDP	Databases	caution	19.1k

risk mix of the 8 listed

caution100%

1 of 8 encrypted

Port :1862MySQL Cluster Manager Agent

Technical Details

Security Information

Related Ports

Port 1862MySQL Cluster Manager Agent