BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-63621High confidence

Apache Camel: Camel-Knative: CloudEvent extension fields received in structured content mode were mapped onto message headers without applying any header filter strategy

Apache Software Foundation · Apache Camel

5.3MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.59% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache Camel and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.camel:camel-knativeECOSYSTEM: introduced 3.15.0; fixed 4.14.94.14.9OSV record ↗aggregator derived · 28 Aug 2026
Mavenorg.apache.camel:camel-knativeECOSYSTEM: introduced 4.15.0; fixed 4.18.44.18.4OSV record ↗aggregator derived · 28 Aug 2026
Mavenorg.apache.camel:camel-knativeECOSYSTEM: introduced 4.19.0; fixed 4.22.04.22.0OSV record ↗aggregator derived · 28 Aug 2026
mavenorg.apache.camel:camel-knative>= 3.15.0, < 4.14.94.14.9GitHub advisory ↗github reviewed aggregator · 28 Aug 2026
mavenorg.apache.camel:camel-knative>= 4.15.0, < 4.18.44.18.4GitHub advisory ↗github reviewed aggregator · 28 Aug 2026
mavenorg.apache.camel:camel-knative>= 4.19.0, < 4.22.04.22.0GitHub advisory ↗github reviewed aggregator · 28 Aug 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-63621 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.apache.camel/camel-knative: Apache Camel Knative: Header injection vulnerability allows server-side request forgery
8 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless
Summary
A flaw was found in Apache Camel Knative component. The Knative consumer in camel-knative improperly handles CloudEvent extension fields in structured content mode, copying them directly into message headers without proper filtering. This allows an unauthenticated attacker to inject internal Camel headers through a specially crafted CloudEvent request. Such injected headers can override configured values when messages are forwarded to other components, leading to server-side request forgery (SSRF), path traversal, or message-dispatch redirection.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-64960

No EUVD known-exploited evidence

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

What

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-64960Official EUVD mapping

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2983Apache Camel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache Camel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren oder sensible Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260826Security Bulletin 26 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Aug 2026, published on 26 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030748Apache Software FoundationのApache Camelにおける複数の脆弱性

Apache Camel Knativeコンポーネントにおける不適切な入力検証および下流コンポーネントで使用される出力中の特殊要素の不適切な無害化（"インジェクション"）の脆弱性について説明します。camel-knativeのKnativeコンシューマは、受信したCloudEvent属性をCamelメッセージヘッダーにマッピングします。バイナリコンテンツモードでは、HTTPヘッダーのパスがKnativeHttpHeaderFilterStrategyを通じてCamel内部ヘッダーをフィルタリングしますが、構造化コンテンツモード（Content-Type: application/cloudevents+json）では、CloudEventの拡張フィールドがJSONボディから直接読み取られ、すべての拡張キーがHeaderFilterStrategyを適用せずにExchangeヘッダーにコピーされます（CloudEventProcessors、仕様バージョン1.0、1.0.1、1.0.2）。その結果、認証されていない攻撃者が構造化モードのCloudEventリクエストを介してCamel内部ヘッダー（例：CamelHttpUri、CamelHttpPath、CamelFileName）をインジェクトでき、Camelのヘッダーマップに対して大文字小文字を区別せずにマッチさせることが可能です。ルートがKnativeコンシューマからヘッダ駆動のコンポーネント（camel-httpやcamel-fileなど）にメッセージを転送する場合、インジェクトされたヘッダーが設定済みの値を上書きし、ルートに応じてサーバー側リクエストフォージェリ（SSRF）、パストラバーサル、またはメッセージディスパッチのリダイレクトを引き起こす可能性があります。これは、バイナリコンテンツモードパスに以前追加されたインバウンドヘッダーフィルタリングの不完全な修正に起因しており、camel-cxf/camel-knative（CVE-2026-47323）、camel-undertow（CVE-2025-30177）、より広範なincoming-header filter（CVE-2025-27636およびCVE-2025-29891）、非HTTPストラテジー（CVE-2026-40453）で対処されたパターンと類似しています。この問題はApache Camelの以下のバージョンに影響を及ぼします：3.15.0から4.14.9未満、4.15.0から4.18.4未満、4.19.0から4.21.0未満です。利用者には問題が修正されたバージョン4.22.0へのアップグレードを推奨します。4.18.xのLTSリリースを利用している場合は4.18.4へのアップグレード、4.14.xのLTSリリースを利用している場合は4.14.9へのアップグレードが推奨されます。非LTSリリースの4.15.0から4.17.0および4.19.0から4.21.0は影響を受けますがメンテナンス修正が提供されないため、これらのバージョンを使用している場合は4.18.4または4.22.0へのアップグレードが推奨されます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 24 Aug 2026 · Last source change 25 Aug 2026, 19:39 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-25
European sourceENISA EUVD · EUVD-2026-64960
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    3.15.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.21.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    3.15.0 < 4.14.9; 4.15.0 < 4.18.4; 4.19.0 < 4.21.0 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-63621 to remediation: access.redhat.com/CVE-2026-63621.
    Before
    remediation: access.redhat.com/CVE-2026-63621
    After
    remediation: access.redhat.com/CVE-2026-63621
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless; camel-knative as a component of Red Hat build of Apache Camel for Spring Boot 4
    After
    openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9 as a component of OpenShift Serverless; openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9 as a component of OpenShift Serverless · Fixed: Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16
    Red Hat Product Security ↗
  6. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-63621 to remediation: access.redhat.com/CVE-2026-63621.
    Before
    remediation: access.redhat.com/CVE-2026-63621
    After
    remediation: access.redhat.com/CVE-2026-63621
    Red Hat Product Security ↗
  7. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: camel.apache.org/CVE-2026-63621.html.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: camel.apache.org/CVE-2026-63621.html
    security@apache.org ↗
  9. SeveritySeverity changed from Unknown to Medium.
    Before
    Unknown
    After
    Medium
    CISA ADP ↗
  10. CVSS scoreCVSS score changed from not recorded to 5.3 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
    Before
    not recorded
    After
    5.3 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
    CISA ADP ↗
  11. ENISA EUVD mappingEUVD-2026-64960 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-64960"}
    ENISA EUVD ↗
  12. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-64960↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-63621 · cve.blacktree.nl