CamelApplication · Apache
CVE-2026-56140
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Input Validation vulnerability in Apache Camel AWS SNS component. The 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. This 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. This 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Camel AWS SNS component (camel-aws2-sns) lacked an inbound filter rule in Sns2HeaderFilterStrategy, unlike its sibling Sqs2HeaderFilterStrategy. While the SQS component was exploitable (CVE-2026-46456), SNS is producer-only and cannot receive messages, so no external attributes map inbound—meaning this was not reachable. The fix adds an inbound filter (setInFilterStartsWith for Camel namespace) as defense-in-depth alignment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CamelApplication
>= 4.0.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify camel-aws2-sns component usageSearch your codebase, build files (pom.xml, build.gradle), and runtime classpaths for the 'camel-aws2-sns' artifact or the 'aws2-sns' component identifierAffected if The camel-aws2-sns component is present in your project dependencies or runtime configuration
-
Check Apache Camel versionRun 'mvn camel:version' for Maven projects, inspect your build artifact manifest, or check the camel-core version in your dependency treeAffected if The installed Camel version falls within: >=4.0.0 AND <4.14.8, OR >=4.15.0 AND <4.18.3, OR >=4.19.0 AND <4.21.0
-
Verify Sns2HeaderFilterStrategy configurationInspect your Camel route definitions and bean configurations for any Sns2HeaderFilterStrategy bean definitions; search for setInFilterStartsWith calls related to SNSAffected if The inbound filter is not explicitly configured (the fix adds this as defense-in-depth)
You are affected only if you use the camel-aws2-sns component with a Camel version in the affected ranges AND you have custom header filter configurations that would benefit from inbound filtering alignment; note that the SNS producer-only design means the original condition was not exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.14.84.18.34.21.0
No urgent action required; upgrade to 4.14.8 (LTS), 4.18.3, or 4.21.0 for aligned configuration. Apply least-privilege IAM permissions as best practice.
4.21.0 (or 4.18.3 for 4.18.x stream, or 4.14.8 for 4.14.x LTS stream)
- 1. Identify all Apache Camel deployments using the camel-aws2-sns component in versions 4.0.0 through 4.14.7, 4.15.0 through 4.18.2, or 4.19.0 through 4.20.x
- 2. Plan an upgrade to one of the fixed versions: 4.21.0 (latest), 4.18.3 (4.18.x stream), or 4.14.8 (4.14.x LTS stream)
- 3. Review the Apache Camel 4.21.0, 4.18.3, or 4.14.8 release notes for any additional changes that may affect your integration
- 4. Execute the upgrade in a non-production environment first to validate functionality
- 5. Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Camel
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data