Due to a mis-written NetworkPolicy, a malicious actor can pivot from the "hardened" namespace to any Pod out of it. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.
Removing the inter-ns NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.
Given your context, delete the failing network policy that should be prefixed by inter-ns- in the target namespace.
{
"cwe_ids": [
"CWE-284"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-16T20:45:59Z",
"nvd_published_at": "2026-03-18T23:17:30Z",
"severity": "HIGH"
}