maven package report

Is org.apache.camel:camel-aws2-sqs safe?

1 known vulnerability, worst severity CRITICAL.

cvss
9.8

how bad it is if exploited, out of 10

epss
0.80%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-cmc3-hr79-8mmv, the advisory selected below

// advisories

GHSA-cmc3-hr79-8mmv

CRITICALCVE-2026-46456

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 Mes

Affected
>= 4.0.0, < 4.14.8
Fixed in
4.14.8
Weakness
CWE-20
Published
2026-07-06
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 02:59 UTC. The most recent advisory here was published 2026-07-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is org.apache.camel:camel-aws2-sqs safe? maven package security report | CyberXYZ