CVE-2026-56140

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper 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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Sep 5, 2026
No patch confirmed yet.
generic

Apache Camel Security Advisory - CVE-2026-56140 - Apache Camel

https://camel.apache.org/security/CVE-2026-56140.html

Vendor Advisories for CVE-2026-56140(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-aws2-sns4.19.0, 4.20.04.21.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 110× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 318 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:11 UTCEG score recompute
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-05 23:13 UTCEG score recompute
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 21:51 UTCEG score recompute
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 08:26 UTCEG score recompute
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 21:59 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 02:21 UTCEG score recompute
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 13:56 UTCGHSA enrichment
  22. 2026-08-25 16:21 UTCEG score recompute
  23. 2026-08-25 16:21 UTCGHSA enrichment
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 12:02 UTCGHSA enrichment
Show 75 more
  1. 2026-08-25 05:24 UTCGHSA enrichment
  2. 2026-08-25 01:06 UTCGHSA enrichment
  3. 2026-08-24 20:49 UTCGHSA enrichment
  4. 2026-08-24 14:23 UTCEG score recompute
  5. 2026-08-24 14:23 UTCGHSA enrichment
  6. 2026-08-24 10:03 UTCEG score recompute
  7. 2026-08-24 10:03 UTCGHSA enrichment
  8. 2026-08-24 04:28 UTCGHSA enrichment
  9. 2026-08-24 00:09 UTCGHSA enrichment
  10. 2026-08-23 19:51 UTCGHSA enrichment
  11. 2026-08-23 15:33 UTCGHSA enrichment
  12. 2026-08-23 11:15 UTCGHSA enrichment
  13. 2026-08-23 06:58 UTCGHSA enrichment
  14. 2026-08-23 02:40 UTCEG score recompute
  15. 2026-08-23 02:39 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-22 22:22 UTCGHSA enrichment
  18. 2026-08-22 18:04 UTCGHSA enrichment
  19. 2026-08-22 13:26 UTCGHSA enrichment
  20. 2026-08-22 09:07 UTCGHSA enrichment
  21. 2026-08-22 04:49 UTCEG score recompute
  22. 2026-08-22 04:49 UTCGHSA enrichment
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 22:45 UTCGHSA enrichment
  25. 2026-08-21 18:28 UTCGHSA enrichment
  26. 2026-08-21 14:10 UTCGHSA enrichment
  27. 2026-08-21 09:01 UTCGHSA enrichment
  28. 2026-08-21 04:43 UTCGHSA enrichment
  29. 2026-08-21 00:25 UTCEG score recompute
  30. 2026-08-21 00:25 UTCGHSA enrichment
  31. 2026-08-20 22:55 UTCEPSS rescore
  32. 2026-08-20 20:07 UTCGHSA enrichment
  33. 2026-08-20 15:49 UTCGHSA enrichment
  34. 2026-08-20 11:10 UTCGHSA enrichment
  35. 2026-08-20 06:52 UTCGHSA enrichment
  36. 2026-08-20 02:34 UTCEG score recompute
  37. 2026-08-20 02:33 UTCGHSA enrichment
  38. 2026-08-19 17:04 UTCEPSS rescore
  39. 2026-08-19 14:09 UTCGHSA enrichment
  40. 2026-08-19 09:50 UTCGHSA enrichment
  41. 2026-08-19 05:29 UTCGHSA enrichment
  42. 2026-08-19 01:09 UTCGHSA enrichment
  43. 2026-08-18 20:49 UTCEG score recompute
  44. 2026-08-18 20:49 UTCGHSA enrichment
  45. 2026-08-18 13:48 UTCEPSS rescore
  46. 2026-08-18 11:00 UTCGHSA enrichment
  47. 2026-08-18 03:50 UTCGHSA enrichment
  48. 2026-08-17 22:42 UTCGHSA enrichment
  49. 2026-08-17 17:12 UTCEG score recompute
  50. 2026-08-17 17:12 UTCGHSA enrichment
  51. 2026-08-17 13:47 UTCEPSS rescore
  52. 2026-08-17 12:52 UTCGHSA enrichment
  53. 2026-08-17 08:34 UTCGHSA enrichment
  54. 2026-08-17 04:17 UTCGHSA enrichment
  55. 2026-08-16 23:59 UTCGHSA enrichment
  56. 2026-08-16 19:41 UTCEG score recompute
  57. 2026-08-16 19:41 UTCGHSA enrichment
  58. 2026-08-16 14:56 UTCEPSS rescore
  59. 2026-08-16 14:49 UTCGHSA enrichment
  60. 2026-08-16 10:30 UTCGHSA enrichment
  61. 2026-08-16 06:13 UTCEG score recompute
  62. 2026-08-16 06:13 UTCGHSA enrichment
  63. 2026-08-16 02:14 UTCEPSS rescore
  64. 2026-08-16 01:56 UTCGHSA enrichment
  65. 2026-08-15 21:38 UTCGHSA enrichment
  66. 2026-08-15 17:19 UTCGHSA enrichment
  67. 2026-08-15 13:01 UTCGHSA enrichment
  68. 2026-08-15 08:43 UTCGHSA enrichment
  69. 2026-08-15 04:25 UTCEG score recompute
  70. 2026-08-15 04:25 UTCGHSA enrichment
  71. 2026-08-15 01:30 UTCEPSS rescore
  72. 2026-08-15 00:07 UTCGHSA enrichment
  73. 2026-08-14 19:49 UTCGHSA enrichment
  74. 2026-08-14 15:32 UTCGHSA enrichment
  75. 2026-08-14 11:14 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56140?
CVE-2026-56140 is a critical vulnerability published on July 6, 2026. Improper 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…
When was CVE-2026-56140 disclosed?
CVE-2026-56140 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56140 actively exploited?
CVE-2026-56140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.5% of all scored CVEs.
What is the CVSS score of CVE-2026-56140?
CVE-2026-56140 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-56140?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56140, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56140

Explore →

Is Your Infrastructure Affected by CVE-2026-56140?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.