How severe is GHSA-mw24-f3xh-j3qv?

No CVSS score has been assigned to GHSA-mw24-f3xh-j3qv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mw24-f3xh-j3qv?

GHSA-mw24-f3xh-j3qv affects the following packages: github.com/ctfer-io/chall-manager/deploy (Go), github.com/ctfer-io/chall-manager/sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-mw24-f3xh-j3qv?

Update github.com/ctfer-io/chall-manager/deploy to 0.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw24-f3xh-j3qv is resolved across your whole dependency graph.

How do I detect GHSA-mw24-f3xh-j3qv in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ctfer-io/chall-manager/deploy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mw24-f3xh-j3qv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mw24-f3xh-j3qv?

O3 pinpoints whether GHSA-mw24-f3xh-j3qv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mw24-f3xh-j3qv actively exploited in the wild?

No public exploit code has been indexed for GHSA-mw24-f3xh-j3qv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mw24-f3xh-j3qv?

GHSA-mw24-f3xh-j3qv has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mw24-f3xh-j3qv?

GHSA-mw24-f3xh-j3qv is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mw24-f3xh-j3qv published, and has it been updated?

GHSA-mw24-f3xh-j3qv was published on March 16, 2026 and was last updated on March 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-mw24-f3xh-j3qv

Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

Also known asCVE-2026-32768GO-2026-4718

Published

Mar 16, 2026

Updated

Mar 26, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk20th percentile+0.22%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐹github.com/ctfer-io/chall-manager/deploy🐹github.com/ctfer-io/chall-manager/sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Due to a mis-written NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. In the specific case of sdk/kubernetes.Kompose it does not isolate the instances.

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 target 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 '^cm-target-'); do
  kubectl -n "$ns" get networkpolicy -o name \
  | grep '^networkpolicy.networking.k8s.io/inter-ns-' \
  | xargs -r kubectl -n "$ns" delete
done

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ctfer-io/chall-manager/deploy`	all versions	0.6.5
🐹Go	`github.com/ctfer-io/chall-manager/sdk`	all versions	0.6.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ctfer-io/chall-manager/deploy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/ctfer-io/chall-manager/deploy to 0.6.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw24-f3xh-j3qv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mw24-f3xh-j3qv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mw24-f3xh-j3qv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Due to a mis-written NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. In the specific case of `sdk/kubernetes.Kompose` it does not isolate the instances. ### 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 faili

O3 Security · Impact-Aware SCA

Is GHSA-mw24-f3xh-j3qv in your dependencies?

O3 detects GHSA-mw24-f3xh-j3qv across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works