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

> A misconfigured NetworkPolicy allows attackers to pivot across namespaces, enabling lateral movement within the monitoring infrastructure.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-7x23-j8gv-v54x, GO-2026-4701

## What is CVE-2026-32720?

CVE-2026-32720 is a high-severity missing authorization vulnerability in ctfer-io monitoring, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-32720?

3 open source packages ship an affected version, including github.com/ctfer-io/monitoring.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.1 |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.1 |
| `github.com/ctfer-io/monitoring` | Go | All versions | 0.2.1 |

## How do I fix CVE-2026-32720?

Upgrade github.com/ctfer-io/monitoring to 0.2.1 or later.

## Is CVE-2026-32720 being exploited?

There is no known exploitation of CVE-2026-32720 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32720 and fix it if it is affected.

What it is: CVE-2026-32720 is a high-severity missing authorization vulnerability in ctfer-io monitoring, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32720 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.1
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.1
- github.com/ctfer-io/monitoring (Go): affected all versions; fixed in 0.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32720/ (Markdown: https://insights.sbomify.com/CVE-2026-32720/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32720
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32720
- OSV: https://osv.dev/vulnerability/CVE-2026-32720

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32720/
Summaries are generated and may contain mistakes; the official description above is the record.