github.com/ctfer-io/monitoring
Affected
- introduced
0, fixed0.2.1(semver)
Fixed versions
0.2.1
Fix
- Fixed version
0.2.1go get github.com/ctfer-io/[email protected]
Advisory
Also known as: CVE-2026-32720, GO-2026-4701
github.com/ctfer-io/monitoring Vulnerable to Improper Access Control
Impact
Due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.
Patch
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.
Workaround
Given your context, delete the failing network policy that should be prefixed by inter-ns- in the monitoring namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.
for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^monitoring-'); do
kubectl -n "$ns" get networkpolicy -o name \
| grep '^networkpolicy.networking.k8s.io/inter-ns-' \
| xargs -r kubectl -n "$ns" delete
doneHigh Basis: The source's own band: HIGH
0, fixed 0.2.1 (semver)0.2.1
0.2.1go get github.com/ctfer-io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0