dbcve.org
FullchainApplication · Ctfer

CVE-2026-32769

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 0.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Fullchain is an umbrella project for deploying a ready-to-use CTF platform. In versions prior to 0.1.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from a subverted application to any Pod out of the origin namespace. The flawed inter-ns NetworkPolicy breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. This issue has been fixed in version 0.1.1. To workaround, delete the failing network policy that should be prefixed by inter-ns- in the target namespace.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Fullchain CTF platform versions before 0.1.1 contain a misconfigured NetworkPolicy with an 'inter-ns-' prefix that improperly allows cross-pod communication within the origin namespace. This breaks the security-by-default isolation model, enabling a compromised application pod to laterally move to any other pod in the namespace.

MitigationUpgrade to version 0.1.1, or as a workaround, delete the NetworkPolicy prefixed with 'inter-ns-' in the affected namespace to restore proper pod isolation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FullchainApplication
Affected:< 0.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Fullchain CTF platform is deployed
    Run 'kubectl get pods --all-namespaces' and look for pods with 'fullchain' or 'ctf' in the name, or check for the presence of the Fullchain deployment via 'kubectl get deployments --all-namespaces | grep -i fullchain'
    Affected if No Fullchain pods or deployments are found in any namespace
  2. Identify the installed Fullchain version
    Run 'kubectl get pods -n <namespace> -o jsonpath="{.items[*].spec.containers[*].image}"' for each namespace where Fullchain is deployed, or check the deployment manifest for the image tag/version
    Affected if The version shown is prior to 0.1.1 (e.g., the image tag does not contain '0.1.1' or higher)
  3. Locate NetworkPolicy resources in Fullchain namespaces
    Run 'kubectl get networkpolicies --all-namespaces' to list all NetworkPolicy objects, then filter to the namespace(s) where Fullchain is installed
    Affected if NetworkPolicy objects exist in the Fullchain namespace
  4. Identify inter-ns- prefixed NetworkPolicy
    Run 'kubectl get networkpolicies -n <fullchain-namespace> -o jsonpath="{.items[*].metadata.name}"' and look for any policy name containing the prefix 'inter-ns-'
    Affected if A NetworkPolicy with name starting with 'inter-ns-' exists in the Fullchain namespace
  5. Examine the inter-ns- NetworkPolicy rules
    Run 'kubectl get networkpolicy <policy-name> -n <namespace> -o yaml' for any inter-ns- policy and inspect the 'spec' section, particularly the 'podSelector', 'policyTypes', and 'ingress' rules to see if they allow traffic from other namespaces
    Affected if The policy allows ingress from pods in other namespaces or does not properly restrict traffic to the same namespace

A user is affected if Fullchain CTF platform version prior to 0.1.1 is installed and a NetworkPolicy prefixed with 'inter-ns-' exists in its namespace, as this misconfiguration permits lateral movement between pods across namespaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.1.1 or later
Fixed in 0.1.1
Vendor patch github.com →
Interim mitigation

Upgrade to version 0.1.1, or as a workaround, delete the NetworkPolicy prefixed with 'inter-ns-' in the affected namespace to restore proper pod isolation.

Recommended fix High confidence

0.1.1

  1. Upgrade Fullchain to version 0.1.1 or later to resolve the miswritten NetworkPolicy vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fullchain Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32769 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data