This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit b174ad3764cb24b4c74aa23a3d8a8e300faf687a Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Jun 15 12:27:06 2026 +0200 Added CVE-2026-48203 Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-48203.md | 17 +++++++++++++++++ content/security/CVE-2026-48203.txt.asc | 31 +++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) diff --git a/content/security/CVE-2026-48203.md b/content/security/CVE-2026-48203.md new file mode 100644 index 00000000..415a9bb7 --- /dev/null +++ b/content/security/CVE-2026-48203.md @@ -0,0 +1,17 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-48203" +date: 2026-06-11T10:00:00+02:00 +url: /security/CVE-2026-48203.html +draft: false +type: security-advisory +cve: CVE-2026-48203 +severity: MEDIUM +summary: "Apache Camel: Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to inject Solr query parameters (server-side request forgery) and document fields" +description: "The camel-solr producer copies Exchange message headers whose names begin with the SolrParam. prefix into the parameters of the Solr request, and headers whose names begin with the SolrField. prefix into the fields of the indexed Solr document. The prefix constants (SolrConstants.HEADER_PARAM_PREFIX / HEADER_FIELD_PREFIX) were the plain strings SolrParam. / SolrField.. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks on [...] +mitigation: "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, routes that set Solr parameters or fields via the raw header prefixes must use CamelSolrParam. / CamelSolrField. instead of SolrParam. / SolrField.. For deployments that cannot upgrade immediately, strip [...] +credit: "This issue was discovered by Yu Bao from PayPal" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23597 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23410 (commit 4578a9014a6b7a914cf16baf2c5bf62a7b163a88) and backported to camel-4.18.x (commit cfc0d51f015b3112eae4ce0968d045f00e95c796) and camel-4.14.x (commit f79cbe3f8bc3fe1095d8492e9ef321289451d457). The fix renames the two camel-solr Exchange header prefix values to the Cam [...] diff --git a/content/security/CVE-2026-48203.txt.asc b/content/security/CVE-2026-48203.txt.asc new file mode 100644 index 00000000..1099e549 --- /dev/null +++ b/content/security/CVE-2026-48203.txt.asc @@ -0,0 +1,31 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-48203" +date: 2026-06-11T10:00:00+02:00 +url: /security/CVE-2026-48203.html +draft: false +type: security-advisory +cve: CVE-2026-48203 +severity: MEDIUM +summary: "Apache Camel: Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to inject Solr query parameters (server-side request forgery) and document fields" +description: "The camel-solr producer copies Exchange message headers whose names begin with the SolrParam. prefix into the parameters of the Solr request, and headers whose names begin with the SolrField. prefix into the fields of the indexed Solr document. The prefix constants (SolrConstants.HEADER_PARAM_PREFIX / HEADER_FIELD_PREFIX) were the plain strings SolrParam. / SolrField.. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks on [...] +mitigation: "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, routes that set Solr parameters or fields via the raw header prefixes must use CamelSolrParam. / CamelSolrField. instead of SolrParam. / SolrField.. For deployments that cannot upgrade immediately, strip [...] +credit: "This issue was discovered by Yu Bao from PayPal" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23597 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23410 (commit 4578a9014a6b7a914cf16baf2c5bf62a7b163a88) and backported to camel-4.18.x (commit cfc0d51f015b3112eae4ce0968d045f00e95c796) and camel-4.14.x (commit f79cbe3f8bc3fe1095d8492e9ef321289451d457). The fix renames the two camel-solr Exchange header prefix values to the Cam [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmovx0kACgkQ406fOAL/ +QQCazgf+M4mOhmr6oW5gC6pbgloAhqg+8ICxBb7Ty2GRAfAhM3/5dRR2wn01YHM9 +B3KThK+a/y3PlvBXc5ACvEflBp2DMv4mTGC+f2Cvg151HLxqQp4UJVpTIjwylv+F +L5VMvazBnVk71Ddhz+wntdm5a+jJgMOORJH5VWibkqK/cpdQMOmI5rnpYjMnBh4/ +5d+UPjEIzEd99+9oFpkTnKaT6nVEJ0VdbrB8U5PzEFgyqI2bzf0GbVVDk/JXlmSW +nXBckMD0sBUU1aOAaE2fSjTt8+aNbQA1adH39pXGr5Y3hjfFd3udoYgSCU8mKcJE +fIfGInY4v8QB1zezi3gS68c6blPCYg== +=rbyf +-----END PGP SIGNATURE-----
