NVD / CVE Program· CNA apache

CVE-2026-45760: Apache Camel K: Camel K Cross-Namespace Build Deputy Attack

HighCVSS 8.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Apache Software Foundation Apache Camel K 2.10.1, 2.8.1, 2.9.2.

Low priority for now. Upgrade to Apache Software Foundation Apache Camel K 2.10.1, 2.8.1, 2.9.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

Published: May 21, 2026
Updated: Jul 23, 2026
EPSS: 0.3% · 25th percentile
CWE: CWE-610

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache Camel K
- 2.0.0 and later · before 2.8.1affected · semver
- 2.9.0 and later · before 2.9.2affected · semver
- 2.10.0 and later · before 2.10.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/apache/camel-k	from 0	—
Go	github.com/apache/camel-k/v2	from 2.10.0 · before 2.10.1	2.10.1
Go	github.com/apache/camel-k/v2	from 2.9.0 · before 2.9.2	2.9.2
Go	github.com/apache/camel-k/v2	before 2.8.1	2.8.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache Camel K	2.10.1	Vendor (CNA)
Apache Software Foundation Apache Camel K	2.8.1	Vendor (CNA)
Apache Software Foundation Apache Camel K	2.9.2	Vendor (CNA)
Go:github.com/apache/camel-k/v2	2.10.1	Package registry (OSV)
Go:github.com/apache/camel-k/v2	2.8.1	Package registry (OSV)
Go:github.com/apache/camel-k/v2	2.9.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.