FKIE_CVE-2026-63621

Vulnerability from fkie_nvd - Published: 2026-08-24 17:17 - Updated: 2026-10-12 15:10
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Summary
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.
References
security@apache.orghttps://camel.apache.org/security/CVE-2026-63621.htmlMailing List, Vendor Advisory
Impacted products
Vendor Product Version
apache camel *
apache camel *
apache camel *
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "org.apache.camel:camel-knative",
          "packageURL": "pkg:maven/org.apache.camel/camel-knative",
          "product": "Apache Camel",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "4.14.9",
              "status": "affected",
              "version": "3.15.0",
              "versionType": "semver"
            },
            {
              "lessThan": "4.18.4",
              "status": "affected",
              "version": "4.15.0",
              "versionType": "semver"
            },
            {
              "lessThan": "4.21.0",
              "status": "affected",
              "version": "4.19.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@apache.org"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "775682D8-3EC1-4CA8-AE1A-9256571A67E9",
              "versionEndExcluding": "4.14.9",
              "versionStartIncluding": "3.15.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "7BC98A81-8301-4163-A47E-C6A9332A2454",
              "versionEndExcluding": "4.18.4",
              "versionStartIncluding": "4.15.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "10DE8B35-C125-4461-A7F7-3BDA3E3CB316",
              "versionEndExcluding": "4.22.0",
              "versionStartIncluding": "4.19.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component (\u0027Injection\u0027) vulnerability in Apache Camel Knative component\n\nThe 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\u0027s 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).\n\n\nThis 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.\n\nUsers 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."
    },
    {
      "lang": "es",
      "value": "Vulnerabilidad de Validaci\u00f3n de entrada incorrecta, Neutralizaci\u00f3n incorrecta de elementos especiales en la salida utilizada por un componente descendente (\u0027Inyecci\u00f3n\u0027) en el componente Apache Camel Knative\n\nEl consumidor de Knative en camel-knative mapea los atributos de CloudEvent entrantes en los encabezados de mensajes de Camel. En modo de contenido binario, la ruta del encabezado HTTP filtra los encabezados internos de Camel a trav\u00e9s de KnativeHttpHeaderFilterStrategy, pero en modo de contenido estructurado (Content-Type application/cloudevents+json) los campos de extensi\u00f3n de CloudEvent se leen directamente del cuerpo JSON y cada clave de extensi\u00f3n se copia en los encabezados de Exchange sin aplicar ninguna HeaderFilterStrategy (CloudEventProcessors, versiones de especificaci\u00f3n 1.0, 1.0.1 y 1.0.2). Como resultado, un atacante no autenticado puede inyectar encabezados internos de Camel (por ejemplo, CamelHttpUri, CamelHttpPath, CamelFileName) a trav\u00e9s de una petici\u00f3n de CloudEvent en modo estructurado, que coincide sin distinci\u00f3n entre may\u00fasculas y min\u00fasculas con el mapa de encabezados de Camel. Cuyo una ruta reenv\u00eda mensajes desde un consumidor de Knative a un componente impulsado por encabezados, como camel-http o camel-file, los encabezados inyectados anulan los valores configurados, lo que permite la falsificaci\u00f3n de petici\u00f3n del lado del servidor (SSRF), el salto de ruta o la redirecci\u00f3n de env\u00edo de mensajes dependiendo de la ruta. Esta es una correcci\u00f3n incompleta del filtrado de encabezados entrantes previamente a\u00f1adido para la ruta en modo de contenido binario, y es el mismo patr\u00f3n abordado en camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), el filtro de encabezados entrantes m\u00e1s amplio (CVE-2025-27636 y CVE-2025-29891), y las estrategias no HTTP (CVE-2026-40453).\n\nEste problema afecta a Apache Camel: desde 3.15.0 antes de 4.14.9, desde 4.15.0 antes de 4.18.4, desde 4.19.0 antes de 4.21.0.\n\nSe recomienda a los usuarios actualizar a la versi\u00f3n 4.22.0, que corrige el problema. Si los usuarios est\u00e1n en la rama de versiones LTS 4.18.x, se les sugiere actualizar a 4.18.4. Si los usuarios est\u00e1n en la rama de versiones LTS 4.14.x, se les sugiere actualizar a 4.14.9. Las versiones no LTS 4.15.0 a 4.17.0 y 4.19.0 a 4.21.0 est\u00e1n afectadas pero no reciben una correcci\u00f3n de mantenimiento; los usuarios de esas versiones deben actualizar a 4.18.4 o 4.22.0."
    }
  ],
  "id": "CVE-2026-63621",
  "lastModified": "2026-10-12T15:10:00.207",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-63621",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-08-25T19:38:54.307849Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-08-24T17:17:58.410",
  "references": [
    {
      "source": "security@apache.org",
      "tags": [
        "Mailing List",
        "Vendor Advisory"
      ],
      "url": "https://camel.apache.org/security/CVE-2026-63621.html"
    }
  ],
  "sourceIdentifier": "security@apache.org",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        },
        {
          "lang": "en",
          "value": "CWE-74"
        }
      ],
      "source": "security@apache.org",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.