Port 6379Redis

Port 6379 (TCP) is the default Redis port, also used by its fork Valkey; change it with port in redis.conf. Cluster nodes also need the cluster bus on 16379 (the data port plus 10000), and Sentinel listens on 26379. Redis has no password by default, so bind it to localhost or a private network, firewall it, and patch CVE-2025-49844 (RediShell).

transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
9/10

critical

lookups
0

rank 993 of 6,667 · top 15%

also known as redis-server, Redis database, Redis cache

Technical Details

what runs on :6379

Redis uses a text-oriented request/response protocol, most commonly RESP2 or RESP3, over a persistent TCP connection. Clients send commands such as GET, SET, and HGET; the server returns typed RESP responses. TCP 6379 is the conventional default port for non-TLS Redis. Redis can be configured for TLS and alternate ports, and clustering, replication, and sentinel deployments use additional configured endpoints and ports.

Related ports

  • 16379: cluster bus, the data port plus 10000 unless set with cluster-port. Both ports must be open between cluster nodes.
  • 26379: Redis Sentinel.

Protected mode

Since Redis 3.2.0, if Redis listens on every interface with no password set, protected mode answers only loopback clients; remote clients get an error telling them to set a password or a bind address. Valkey uses the same ports, and its documentation notes that by default it binds to all interfaces with no authentication.

Security Information

exposure of :6379

risk score

9/ 10critical

assume it is being scanned right now. do not expose this port to untrusted networks; put a vpn or bastion in front of it.

databases averages 3.8 across 176 ports — this one sits 5.2 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

every listening transport is another surface to filter at the edge

security overview

Redis should not be exposed directly to the public internet. An unauthenticated or weakly authenticated instance can allow an attacker to read or modify application data, delete keys, abuse administrative commands, or use configuration and module-loading features for further compromise, depending on version and configuration. Restrict access with network controls, require strong authentication and authorization, and use TLS where traffic crosses an untrusted network.

Known vulnerabilities

  • CVE-2025-49844 ("RediShell", CVSS 9.9): a use-after-free in the Lua scripting engine lets an authenticated client run code on the host. Fixed on 2025-10-03 in 6.2.20, 7.2.11, 7.4.6, 8.0.4 and 8.2.2. On an instance with no password, any client counts as authenticated.
  • P2Pinfect (2023–24) spread through exposed Redis servers, using the CVE-2022-0543 Lua sandbox escape and replication abuse.

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

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted