oscerd opened a new issue, #140: URL: https://github.com/apache/camel-kit/issues/140
## Description The Knowledge MCP server depends on `camel-catalog` for endpoint-URI validation metadata (`DefaultCamelCatalog.validateEndpointProperties`). Dependency scanners (Trivy/OSV) report Critical CVEs for Camel runtime components such as `camel-jms` (e.g. CVE-2026-40453 / CVE-2026-40860). The server **never constructs or runs** a JMS/Kafka/etc. route — it only reads catalog metadata — so these are not reachable. Note: in a review, the two Trivy CRITICALs actually traced to a `camel-kit-graph` **test-fixture POM** (`src/test/resources/testdata/di/pom.xml`) used as *parser input*, not to a real dependency. Still worth confirming the shipped runner uber-jar's real transitive set. ## Proposed change Inspect the `knowledge/mcp` runner uber-jar (`./mvnw -pl knowledge/mcp -am dependency:tree` and/or list the uber-jar contents). If uninvoked Camel runtime components are bundled transitively via `camel-catalog`, exclude them to shrink the shipped artifact and silence scanner noise. If they are not bundled, document that the catalog dependency is metadata-only. ## Notes Dependency hygiene; the reported CVEs are **not reachable** from the MCP server. _AI-generated by Claude Code (Claude Opus 4.8) on behalf of @oscerd._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
