Port 10086 — Unassigned, But Not Empty

What This Port Is

Port 10086 is a registered port (in the range 1024-49151), which means it's officially unassigned by IANA. There's no standard protocol, no RFC, no official "this is what port 10086 does" decree.

But here's the thing: it doesn't sit empty.

What Actually Uses It

Seeyon OA Mobile Gateway

Port 10086 commonly hosts Seeyon OA, an enterprise collaboration platform popular in Asia. Specifically, the mobile gateway runs here, handling HTTP APIs and document handling for Seeyon's office automation system.¹

This matters because Seeyon has had documented remote code execution vulnerabilities affecting port 10086. These aren't theoretical—they've been actively exploited in the wild to deploy webshells and cryptominers.² When you find port 10086 open on a Seeyon system, you're looking at a potential attack surface.

NetBackup SPWS

Veritas NetBackup uses port 10086 for SPWS (Secure Process Web Services) on WORM (Write Once, Read Many) storage servers.³ This is infrastructure-level usage—backup and archival systems.

What the Lack of Assignment Means

Unassigned ports are the frontier. They're where applications stake claims without asking permission. This creates three realities:

1. Discovery failure: Your port scanning tool won't tell you what's running. It'll just say "open" or "filtered." You have to know what to look for, or you have to actually talk to it.

2. Security ambiguity: No official documentation. No RFC explaining security properties. Just whoever's running Seeyon or NetBackup on that box, and whatever vulnerabilities ship with it.

3. Silent multiplicity: The same port might mean different things on different networks. On one server it's Seeyon. On another it's a custom application nobody documented.

How to Check What's Listening

# On your machine, is anything listening on 10086?
netstat -an | grep 10086
ss -an | grep 10086

# On a remote machine (if you have permission)
nc -zv <hostname> 10086

# Nmap (common for scanning)
nmap -p 10086 <hostname>

# Connect to see what it says (be careful)
curl http://localhost:10086
curl https://localhost:10086 --insecure

# Or with telnet if the service is text-based
telnet localhost 10086

If port 10086 answers, try to identify what by looking at:

• The HTTP headers (request something and read the response)
• Error messages
• Try common paths: /admin, /api, /mobile
• Check if it's Seeyon: look for paths like /oa, /seeyon

Why Unassigned Ports Matter

The IANA port registry is comprehensive—there are thousands of assigned ports. But new protocols, new applications, new services get created faster than assignments get handed out. Unassigned ports aren't forgotten space; they're actively used space. They're where the Internet innovates, and where it also hides.

When a port is unassigned, there's no official "how to secure this" document. Security is whatever the application developer decided. For something like Seeyon OA, that's meant real vulnerabilities reaching real production systems.

The absence of assignment doesn't mean absence of importance. It means you have to look harder.