{"cve":"CVE-2026-56140","nvd":{"published":"2026-07-06T09:16:39.280","modified":"2026-07-09T13:02:06.630","status":"Analyzed","description":"Improper Input Validation vulnerability in Apache Camel AWS SNS component.\n\n\nThe camel-aws2-sns component filters Camel headers through a component-specific HeaderFilterStrategy, Sns2HeaderFilterStrategy. Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule. For the related camel-aws2-sqs component this inbound gap was exploitable, because the Sqs2Consumer maps inbound SQS message attributes into the Camel Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, allowing a message sender to inject Camel control headers (tracked as CVE-2026-46456). camel-aws2-sns, by contrast, is producer-only: Sns2Endpoint does not support consumers (createConsumer throws UnsupportedOperationException, 'You cannot receive messages from this endpoint'), so no externally-supplied message attributes are ever mapped inbound into a Camel Exchange through SNS, and the missing inbound filter rule on Sns2HeaderFilterStrategy was therefore not reachable by an attacker. As part of the same fix (CAMEL-23506), an inbound filter rule (setInFilterStartsWith for the Camel namespace) was added to Sns2HeaderFilterStrategy so that its configuration matches the corrected Sqs2HeaderFilterStrategy and the other sibling strategies. This is a defense-in-depth alignment with no known exploit path in camel-aws2-sns.\n\n\nThis issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.\n\nThis is a defense-in-depth hardening change with no known exploit path in camel-aws2-sns, which is producer-only, so no urgent action or workaround is required. Users who want the aligned behaviour can upgrade to version 4.21.0, or to 4.14.8 on the 4.14.x LTS releases stream, or to 4.18.3 on the 4.18.x releases stream, which contain the change. As a general best practice, operators should continue to apply least-privilege IAM permissions on their SNS topics.","cvss_v4":null,"cvss_v3":{"version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8},"cwes":["CWE-20"],"references":["https://camel.apache.org/security/CVE-2026-56140.html"],"products":["apache:camel"],"source":"nvd","synced_at":"2026-10-19T22:42:16.820116992+00:00"},"epss":{"cve":"CVE-2026-56140","score":0.00738,"percentile":0.54561,"date":"2026-10-31"},"kev":null,"osv":[{"id":"GHSA-w2v8-8q6c-3rhr","url":"https://osv.dev/vulnerability/GHSA-w2v8-8q6c-3rhr","summary":"Apache Camel-AWS2-SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy","modified":"2026-08-26T14:56:27.055033Z","packages":[{"ecosystem":"Maven","name":"org.apache.camel:camel-aws2-sns","purl":"pkg:maven/org.apache.camel/camel-aws2-sns","ranges":[">=4.0.0 <4.14.8"],"fixed":["4.14.8"]},{"ecosystem":"Maven","name":"org.apache.camel:camel-aws2-sns","purl":"pkg:maven/org.apache.camel/camel-aws2-sns","ranges":[">=4.15.0 <4.18.3"],"fixed":["4.18.3"]},{"ecosystem":"Maven","name":"org.apache.camel:camel-aws2-sns","purl":"pkg:maven/org.apache.camel/camel-aws2-sns","ranges":[">=4.19.0 <4.21.0"],"fixed":["4.21.0"]}]}],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}