GHSA-7X23-J8GV-V54X

Vulnerability from github – Published: 2026-03-13 20:58 – Updated: 2026-03-16 22:00
VLAI?
Summary
github.com/ctfer-io/monitoring Vulnerable to Improper Access Control
Details

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
done
Severity ?
7.1 (High)
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
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/ctfer-io/monitoring"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.2.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32720"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-13T20:58:28Z",
    "nvd_published_at": "2026-03-16T14:19:43Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nDue to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace.\nThis breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.\n\n### Patch\n\nRemoving 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.\n\n### Workaround\n\nGiven your context, delete the failing network policy that should be prefixed by `inter-ns-` in the monitoring namespace.\nYou can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.\n\n```bash\nfor ns in $(kubectl get ns -o jsonpath=\u0027{.items[*].metadata.name}\u0027 | tr \u0027 \u0027 \u0027\\n\u0027 | grep \u0027^monitoring-\u0027); do\n  kubectl -n \"$ns\" get networkpolicy -o name \\\n  | grep \u0027^networkpolicy.networking.k8s.io/inter-ns-\u0027 \\\n  | xargs -r kubectl -n \"$ns\" delete\ndone\n```",
  "id": "GHSA-7x23-j8gv-v54x",
  "modified": "2026-03-16T22:00:32Z",
  "published": "2026-03-13T20:58:28Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ctfer-io/monitoring/security/advisories/GHSA-7x23-j8gv-v54x"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32720"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ctfer-io/monitoring/pull/168"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ctfer-io/monitoring/commit/5404a11863b32b14ee5c62d1215352ab519d4edb"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ctfer-io/monitoring"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ctfer-io/monitoring/releases/tag/v0.2.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "github.com/ctfer-io/monitoring Vulnerable to Improper Access Control"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.