dbcve.org
CWE-610Weakness · CWE-610

CVE-2026-45760

HIGH · 8.1 CVSS v3.1 Published 2026-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
(Externally Controlled Reference to a Resource in Another Sphere), (Authorization Bypass Through User-Controlled Key) vulnerability in Apache Camel K. Authorized users in a Kubernetes namespace can create a Build resource, controlling the Pod generation in a namespace of their choice, including the operator namespace. This issue affects Apache Camel K: from 2.0.0 before 2.8.1, from 2.9.0 before 2.9.2, from 2.10.0 before 2.10.1. Users are recommended to upgrade to version 2.10.1 (or 2.8.1 or 2.9.2), which fixes the issue.

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

This is an authorization bypass vulnerability in Apache Camel K where users with permission to create Build resources can control Pod generation in arbitrary Kubernetes namespaces, including the operator namespace. The vulnerability stems from insufficient validation of namespace boundaries in the Build resource controller, allowing privilege escalation across namespace boundaries.

MitigationUpgrade Apache Camel K to version 2.10.1 (or 2.8.1 or 2.9.2) to remediate this authorization bypass that allows controlled Pod generation in unauthorized namespaces.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Identify Apache Camel K version
    Run 'kubectl get deployment camel-k-operator -n <operator-namespace> -o jsonpath="{.spec.template.spec.containers[0].image}"' or check Helm release if installed via Helm
    Affected if The version is before 2.10.1, 2.9.2, or 2.8.1
  2. Verify Build API existence
    Run 'kubectl api-resources | grep -i build' to confirm Build custom resource definition is installed in the cluster
    Affected if Build resources are defined in the cluster and Camel K version is vulnerable
  3. Check user permissions for Build creation
    Run 'kubectl auth can-i create builds --as=<user>' in a non-operator namespace to test if authorized users can create Build resources
    Affected if Users with permissions to create Builds in any namespace can potentially exploit this flaw
  4. Examine RBAC for cross-namespace Build privileges
    Review ClusterRoleBindings and RoleBindings related to Camel K: 'kubectl get clusterrolebindings -l app.kubernetes.io/name=camel-k' and check for overly permissive rules on Build resources
    Affected if ClusterRole or Role grants create/update permissions on Builds across namespaces without proper namespace scoping
  5. Audit existing Build resources in non-operator namespaces
    Run 'kubectl get builds --all-namespaces' to list any Build resources created in namespaces other than the operator namespace
    Affected if Build resources exist in namespaces other than the operator namespace, indicating the feature is in use and potentially exploitable

You are affected if Apache Camel K version is below 2.10.1 (or 2.9.2/2.8.1) and Build resources can be created by users who should be restricted to their own namespace.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Camel K to version 2.10.1 (or 2.8.1 or 2.9.2) to remediate this authorization bypass that allows controlled Pod generation in unauthorized namespaces.

Recommended fix High confidence

2.10.1 (or 2.9.2 or 2.8.1 depending on current version)

  1. Identify the current Apache Camel K version running in the cluster using 'kubectl get csv -n <namespace>' or checking the operator deployment
  2. Determine the appropriate upgrade path based on current version: upgrade to 2.10.1 if coming from 2.10.0, or 2.9.2 if coming from 2.9.0-2.9.1, or 2.8.1 if coming from 2.0.0-2.8.0
  3. Review the Apache Camel K release notes for the target version to understand any migration requirements
  4. Back up current Camel K custom resources (Build, Integration, Kamelet, etc.) using 'kubectl get all -n <namespace> -o yaml > backup.yaml'
  5. Upgrade the Camel K operator using the official installation method: 'kamel install --upgrade' for OperatorHub installations, or upgrade via OLM/OLM catalog
  6. Verify the upgrade completed successfully by checking 'kamel version' and confirming operator pod is running
  7. Confirm the vulnerability is resolved by verifying RBAC policies prevent cross-namespace Build resource creation
Caveat Review release notes for any breaking changes between versions; minor/patch upgrades typically safe but test in non-production first

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45760 — 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-45760 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