Apache camel是美国Apache基金会开源的一个企业集成模式框架。 Apache Camel存在输入验证错误漏洞,该漏洞源于输入验证不当,即camel-aws2-sns组件通过Sns2HeaderFilterStrategy过滤Camel标头时未配置入站过滤规则,可能导致未授权攻击者利用网络访问注入Camel控制标头。以下版本受到影响:4.0.0至4.14.8之前版本、4.15.0至4.18.3之前版本和4.19.0至4.21.0之前版本。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Apache Software Foundation | Apache Camel AWS2 SNS | 4.0.0< 4.14.8 |
affected |
4.15.0< 4.18.3 |
affected | ||
4.19.0< 4.21.0 |
affected |
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Apache Software Foundation | Apache Camel AWS2 SNS | 4.0.0 ~ 4.14.8 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-46457 | Apache Camel: Camel-NATS: Inbound NATS message headers are mapped into the Exchange withou | |
| CVE-2026-48205 | Apache Camel DNS: The dns.* and term Exchange header constants used non-Camel-prefixed nam | |
| CVE-2026-48204 | Apache Camel: Camel-MongoDB-GridFS: The gridfs.* control headers used non-Camel-prefixed n | |
| CVE-2026-48203 | Apache Camel: Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non- | |
| CVE-2026-46726 | Apache Camel Vertx Websocket: The inbound consumer maps externally-supplied WebSocket quer | |
| CVE-2026-46592 | Apache Camel: Camel-CXF: The SOAP operation-selection headers used non-Camel-prefixed name | |
| CVE-2026-46591 | Apache Camel: Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header a | |
| CVE-2026-46590 | Apache Camel: Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle manager | |
| CVE-2026-46585 | Apache Camel Lucene: The query control headers used non-Camel-prefixed names (QUERY, RETUR | |
| CVE-2026-46584 | Apache Camel Mail: The mail producer applied attacker-supplied message headers as JavaMail | |
| CVE-2026-48206 | Apache Camel JIRA: A set of non-Camel-prefixed Exchange header constants bypass the HTTP h | |
| CVE-2026-46456 | Apache Camel: Camel-AWS2-SQS: Inbound message attributes are mapped into the Exchange with | |
| CVE-2026-46455 | Apache Camel: Camel-Keycloak: The access-token validity window is not verified because the | |
| CVE-2026-46454 | Apache Camel: Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange wi | |
| CVE-2026-46453 | Apache Camel: Camel-Elasticsearch-Rest-Client: Exchange header constants without the Camel | |
| CVE-2026-43865 | Apache Camel: Camel-Hazelcast: Unsafe Java deserialization in default-configured managed H | |
| CVE-2026-42527 | Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables | |
| CVE-2026-40859 | Apache Camel: Camel-Vertx-Http: Unsafe Java deserialization of HTTP response bodies via a | |
| CVE-2026-40047 | Apache Camel: Camel-Docling: Insufficient validation of custom CLI arguments enables argum | |
| CVE-2026-56139 | Apache Camel Undertow: The muteException consumer option defaulted to false, so a processi |
Showing top 20 of 39 CVEs. View all on vendor page → →
No comments yet