Docker Bypasses UFW Firewall Exposing PostgreSQL and Redis Ports to Rapid Malware Infections
A typical migration to a fresh VPS begins with basic hardening on Ubuntu or Debian using UFW with default deny incoming and only ports 22, 80, and 443 allowed. After confirming UFW status shows no unexpected listeners, Docker is installed and a compose file launches backend services including PostgreSQL and Redis with explicit port mappings such as "5432:5432" for convenient remote access via tools like DBeaver.
Within days, abuse reports arrive from the hosting provider or monitoring alerts trigger as CPU usage spikes from processes like kdevtmpfsi or kinsing, while database tables are replaced by ransom notes demanding Bitcoin. The root cause lies in how Docker manipulates Netfilter tables, bypassing UFW entirely.
Netfilter Bypass Mechanism
Docker enables IP forwarding and creates bridge interfaces such as docker0 and br-xxxx for each compose stack. It inserts DNAT rules into the nat PREROUTING chain that rewrite destination addresses from the host's public IP to internal container IPs like 172.18.0.2 before routing decisions occur. Traffic then enters the FORWARD chain where Docker's DOCKER-FORWARD and DOCKER chains appear above UFW's ufw-before-forward rules, granting ACCEPT for the mapped ports.
Testing with netcat from an external machine confirms both 5432 and 6379 respond despite UFW verbose status showing only SSH and web ports allowed. The ss command reveals docker-proxy listening on 0.0.0.0 and [::] for these ports.
IPv6 Exposure Risks
Starting with Docker 27.0, ip6tables management activates by default. Administrators who configure protections only in IPv4 tables or set IPV6=no in ufw defaults leave IPv6 sockets open. Hetzner and similar providers assign public /64 prefixes, allowing scanners to reach [::]:5432 even when IPv4 is blocked.
Bot Activity Timeline and Techniques
Cloud IP ranges are continuously scanned by masscan and zmap for database ports. In one documented case on a Hetzner CPX21 instance running Qdrant, Redis, and PostgreSQL, the first REPLICAOF connection arrived 1 minute 52 seconds after container startup.
- For Redis without authentication, bots issue FLUSHALL then attempt CONFIG SET to write cron jobs or load malicious modules via replication.
- Older images remain vulnerable to CVE-2022-0543 Lua escapes on Debian-based builds.
- PostgreSQL instances with weak default credentials such as postgres:password123 are directly accessible for data exfiltration or ransomware deployment.
Similar incidents affected Spree Commerce starter templates where maintainers noted the configuration was intended only for local development.
Related articles
Chrome Researcher Edits Own VRP Reward to $1.3M in Bug Tracker Prank, Triggering AI Misinformation Spread
Security researcher Lyra Rebane, who has disclosed 14 CVEs in Chrome, reported a logical flaw in the Background Fetch API in 2022 that could enable browser-based botnets. Google awarded $1,000 after the issue was fixed in February 2026, but the researcher later received verifier rights in the Buganizer tracker. She jokingly set the vrp-reward field to $1,333,337, the largest amount in Google VRP history. The tweet about the edit went viral and was picked up by AI news generators and Google search, which began listing her as a millionaire. Community Notes initially flagged the post before an experimental AI note incorrectly claimed the screenshot was edited. The incident highlights how social media amplification and AI systems can turn a harmless joke into persistent misinformation across search engines including Kagi, DuckDuckGo, and Bing.
Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK
Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a critical flaw in the HotSpot JVM that enables memory corruption via a malicious Base64 payload. The issue affects multiple OpenJDK distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu when running on modern Intel Xeon and AMD EPYC processors supporting AVX-512 VBMI instructions. Rated 9.2 on CVSS 4.0, the vulnerability can lead to data theft and arbitrary code execution without authentication in several widely used products such as Keycloak, Jenkins and Atlassian Jira. Public exploit code and reconnaissance activity were observed within days, although no confirmed successful breaches have been reported yet. Patches are available for supported branches, while older intermediate versions require migration to maintained releases.
F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway
Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.
NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2
On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.