dbcve.org
CamelApplication · Apache

CVE-2026-46456

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 4.14.8 / 4.18.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

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 · unedited
Improper Input Validation vulnerability in Apache Camel AWS2-SQS Component. The camel-aws2-sqs component map inbound message attributes into the Camel Exchange through a component-specific HeaderFilterStrategy. Sqs2HeaderFilterStrategy configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers being written to the broker) but did not configure an inbound filter. As a result, when Sqs2Consumer copies each SQS MessageAttribute into the Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, DefaultHeaderFilterStrategy applied no inbound rule and treated every header name as not filtered - including Camel-internal control headers such as CamelHttpUri, CamelFileName or CamelSqlQuery - copying them unmodified onto the Camel message. Any principal able to send messages to the consumed SQS queue (for example a cross-account sender or a lower-privileged in-account component holding sqs:SendMessage) could therefore set arbitrary Camel control headers that influence the behaviour of downstream producers in the route (for example redirecting an HTTP producer, changing a file name, or overriding a query); the injected headers also persist across internal direct, seda and vm hops. The concrete downstream impact depends on which producers the route uses. 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. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix adds an inbound HeaderFilterStrategy rule to Sqs2HeaderFilterStrategy that filters the Camel header namespace case-insensitively on inbound mapping, so sender-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from inbound messages before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), and restrict who may send to the consumed SQS queue by applying least-privilege sqs:SendMessage permissions on the queue resource policy.

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 confidence

The Sqs2HeaderFilterStrategy in Apache Camel AWS2-SQS component only configured an outbound filter but failed to configure an inbound filter, causing all SQS message attributes to be copied into the Camel Exchange without filtering. This allows any principal with sqs:SendMessage permission to inject arbitrary Camel control headers (CamelHttpUri, CamelFileName, CamelSqlQuery, etc.) that manipulate downstream producer behavior.

MitigationUpgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams). If immediate upgrade is not possible, add removeHeaders('Camel*') and removeHeaders('camel*') at the start of affected routes and apply least-privilege sqs:SendMessage permissions.

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
Affected:>= 4.0.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine Apache Camel version
    Check your project's Camel version in pom.xml, build.gradle, or runtime (e.g., org.apache.camel.CamelContext.getVersion()). Compare against affected ranges: >= 4.0.0 < 4.14.8, >= 4.15.0 < 4.18.3, or >= 4.19.0 < 4.21.0
    Affected if Your Camel version falls within any of the affected version ranges
  2. Confirm AWS2-SQS component usage
    Search your codebase for camel-aws2-sqs dependency in build files, or look for aws2-sqs in route definitions (e.g., from("aws2-sqs://...")). Check if your routes consume from SQS endpoints.
    Affected if Your application uses the AWS2-SQS component to consume messages from Amazon SQS
  3. Inspect SQS consumer route configuration
    Examine routes that use aws2-sqs consumer (from("aws2-sqs://...")) and check if removeHeaders("Camel*") or similar header filtering is explicitly configured before processing. Review the full route definition.
    Affected if Routes consuming from SQS lack explicit header filtering (removeHeaders) for inbound messages
  4. Check for injected Camel control headers in messages
    Add logging or inspection in your route to output all message headers from SQS consumers. Look for headers such as CamelHttpUri, CamelFileName, CamelSqlQuery, CamelHttpQuery, or other Camel* headers that were not set by your application.
    Affected if Camel control headers (prefixed with Camel or camel) appear in exchange headers originating from SQS messages

You are affected if you run a vulnerable Camel version (4.0.0-4.14.7, 4.15.0-4.18.2, or 4.19.0-4.20.x) and use AWS2-SQS to consume messages without explicit inbound header filtering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.14.8 / 4.18.3 / 4.21.0 or later
Fixed in 4.14.84.18.34.21.0
Interim mitigation

Upgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams). If immediate upgrade is not possible, add removeHeaders('Camel*') and removeHeaders('camel*') at the start of affected routes and apply least-privilege sqs:SendMessage permissions.

Recommended fix High confidence

4.21.0 (or 4.14.8 for 4.14.x LTS, or 4.18.3 for 4.18.x stream)

  1. 1. Identify the current Apache Camel version in use by checking the project dependencies (e.g., pom.xml for Maven projects).
  2. 2. Determine the appropriate upgrade target based on the current version: if on 4.14.x stream, upgrade to 4.14.8; if on 4.18.x stream, upgrade to 4.18.3; otherwise upgrade to 4.21.0.
  3. 3. Update the Maven dependency or build configuration to use the fixed Camel version (e.g., change org.apache.camel:camel-aws2-sqs to the target version).
  4. 4. Rebuild and test the application to verify the upgrade does not break existing functionality.
  5. 5. If using 4.21.0 is not feasible and immediate upgrade is not possible, add removeHeaders('Camel*') and removeHeaders('camel*') at the start of any route consuming from SQS to strip control headers from inbound messages as a compensating control.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46456 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46456 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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