CVE-2026-46592

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Improper Input Validation, Unintended Proxy or Intermediary ('Confused Deputy') vulnerability in Apache Camel CXF SOAP component.

The camel-cxf producer selects which SOAP operation to invoke on the backend service from the operationName (and operationNamespace) Exchange header, whose constant values (CxfConstants.OPERATION_NAME / OPERATION_NAMESPACE) were the plain strings operationName / operationNamespace. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a cxf: producer, any HTTP client could therefore set the operationName header and have CxfProducer resolve and invoke a different WSDL operation than the route intended - for example replacing a read operation with a destructive one - against the backend SOAP service (a confused-deputy redirection). The constant is defined in the shared camel-cxf-common module, so the same non-prefixed names also applied to camel-cxfrs. No credentials are required when the bridging consumer is unauthenticated. 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. After upgrading, the operation-selection headers are named CamelCxfOperationName / CamelCxfOperationNamespace and are filtered at transport boundaries; see the 4.21 upgrade guide for the cross-transport carrier-header pattern. For deployments that cannot upgrade immediately, do not select the CXF operation from untrusted input: strip the operationName and operationNamespace headers from any untrusted ingress before the cxf: producer and set the operation from a trusted source in the route.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-46592: Apache Camel: Camel-CXF: The SOAP operation-selection headers used non-Camel-prefixed names (operationName, operationNamespace) that bypass the HTTP header filter, allowing an HTTP client to redirect the invoked SOAP operation

http://www.openwall.com/lists/oss-security/2026/07/05/15
generic

Apache Camel Security Advisory - CVE-2026-46592 - Apache Camel

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

Vendor Advisories for CVE-2026-46592(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcamel-cxf-common2026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 145× 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 184 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46592?
CVE-2026-46592 is a high vulnerability published on July 6, 2026. Improper Input Validation, Unintended Proxy or Intermediary ('Confused Deputy') vulnerability in Apache Camel CXF SOAP component. The camel-cxf producer selects which SOAP operation to invoke on the backend service from the operationName (and operationNamespace) Exchange header, whose constant…
When was CVE-2026-46592 disclosed?
CVE-2026-46592 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46592 actively exploited?
CVE-2026-46592 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46592?
CVE-2026-46592 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-46592?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46592, 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

Explore the affected products and dependency analysis for CVE-2026-46592

Explore →

Is Your Infrastructure Affected by CVE-2026-46592?

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

Start Free Scan →Browse All CVEs