Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45760 high CVSS 8.1

Vulnerability in github.com/apache/camel-k/v2 (CVE-2026-45760)

Summary

Vulnerability in github.com/apache/camel-k/v2 (CVE-2026-45760). Confidential information can be exposed externally. Mitigation: upgrade to 2.10.1 or later.

Original description

The description as published by the source.

(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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45760 has been found in github.com/apache/camel-k/v2.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/apache/camel-k/v2 to 2.10.1 or later.
If unsure, ask your IT team or search "github.com/apache/camel-k/v2 CVE-2026-45760" on the vendor's site.

CVE-2026-45760 (github.com/apache/camel-k/v2) — CWE-610 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.10.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-610) exists in github.com/apache/camel-k/v2.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/apache/camel-k/v2.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.10.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/apache/camel-k/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/apache/camel-k/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/apache/camel-k/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/apache/camel-k/v2 to 2.10.1

    ステージング環境で 2.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/apache/camel-k/v2
[{"type":"SEMVER","events":[{"introduced":"2.10.0"},{"fixed":"2.10.1"}]}]
Go github.com/apache/camel-k
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details