Habr•August 11, 2026•🇷🇺Translated from Russian

5 NetworkPolicy Mistakes That Leave Kubernetes Clusters Completely Unprotected

Kubernetes NetworkPolicy objects can exist in the API without actually restricting any traffic, creating a false sense of security that only surfaces during penetration tests. The original Russian article from OTUS details five critical mistakes that produce exactly this outcome: policies are visible via kubectl get networkpolicy yet traffic flows freely.

CNI Plugin Does Not Support NetworkPolicy

Kubernetes stores NetworkPolicy objects but relies on the Container Network Interface plugin for enforcement. Plugins such as Calico, Cilium, and Weave Net implement them, while plain Flannel and kubenet do not. Administrators can confirm the plugin by checking pods in the kube-system namespace, yet the most reliable test applies a deny-all policy in a test namespace and attempts cross-namespace connectivity with tools like nicolaka/netshoot.

Default-Deny Egress Blocks DNS Resolution

Applying an egress deny-all rule immediately breaks name resolution because queries to CoreDNS on port 53 are also blocked. Applications report UnknownHostException or timeouts rather than access denied errors, leading teams to investigate the DNS service instead of the policy. The recommended fix adds a separate policy allowing UDP and TCP traffic to the kube-dns pods in the kube-system namespace.

Single Dash Creates Cluster-Wide Access

A misplaced dash in the YAML turns an AND condition into an OR condition. The correct structure places namespaceSelector and podSelector under the same list item so that only pods matching both labels are permitted. When separated by an extra dash, any pod bearing the label app: api from any namespace gains access, silently expanding the attack surface.

namespaceSelector Matches Labels, Not Namespace Names

The selector matchLabels: name: monitoring looks for a label on the namespace object, not its name. Most namespaces only carry the automatic label kubernetes.io/metadata.name. Administrators must either use this built-in label or manually apply custom labels, understanding that custom labels can be forgotten on newly created namespaces.

Confusion Between Protected Pods and Allowed Sources

The top-level podSelector defines which pods the policy protects, while selectors inside from or to blocks define allowed peers. Swapping these produces a policy with an empty from: [] list that permits traffic from everywhere. An empty ingress list without any rules denies all ingress, whereas a rule containing an empty source list allows all sources.

Additional coverage gaps remain even with correct policies: pods using hostNetwork: true bypass the CNI, intra-pod localhost traffic between containers is uncontrolled, and response traffic for established connections is automatically permitted. The article advises starting with traffic tests, rolling out default-deny together with DNS allowances, using policy audit modes in Calico and Cilium, and keeping a single-command rollback ready.

Related articles

Security NEXT•Vulnerabilities & Exploits

PHP Releases Security Updates Fixing 18 Vulnerabilities Including Multiple Critical Issues

The PHP development team has published security updates addressing 18 vulnerabilities across four supported branches. Four of the flaws received a CVSSv4.0 base score of 9.2 and affect session handling functionality. CVE-2026-115560 allows unintended object injection when different session serialization formats are mixed in the same environment. CVE-2026-126714 can lead to restoration of malicious objects if a session file write operation is interrupted before completion. The updates cover PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 and were released on 19 November 2026 after an advance notice the previous day. Twelve of the issues are common to all four branches. The patches close the possibility of remote arbitrary code execution under specific conditions.

Security NEXT•Vulnerabilities & Exploits

Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST

A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.

BoletimSec•Vulnerabilities & Exploits

Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms

A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.

BoletimSec•Vulnerabilities & Exploits

Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution

Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.