{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-33454", "tracking": { "current_release_date": "2026-04-29T15:49:15.545592Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-33454", "initial_release_date": "2026-04-27T07:35:20.245780Z", "revision_history": [ { "date": "2026-04-27T07:35:20.245780Z", "number": "1", "summary": "NCSC Score created." }, { "date": "2026-04-27T10:38:53.591873Z", "number": "2", "summary": "Source created.| CVE status created. (valid)| Description created for source.| Products connected (2).| References created (1).| CWES updated (1)." }, { "date": "2026-04-27T10:38:55.175159Z", "number": "3", "summary": "NCSC Score updated." }, { "date": "2026-04-27T11:19:26.171710Z", "number": "4", "summary": "Source connected.| CVE status created. (valid)| Products connected (2).| References created (10)." }, { "date": "2026-04-27T11:19:31.397136Z", "number": "5", "summary": "NCSC Score updated." }, { "date": "2026-04-27T11:34:17.821185Z", "number": "6", "summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (1).| CWES updated (1)." }, { "date": "2026-04-27T11:34:19.874654Z", "number": "7", "summary": "NCSC Score updated." }, { "date": "2026-04-27T15:17:56.973650Z", "number": "8", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-04-27T15:18:00.116694Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-04-27T15:40:47.065772Z", "number": "10", "summary": "CVSS created.| Unknown change." }, { "date": "2026-04-27T15:40:59.240932Z", "number": "11", "summary": "NCSC Score updated." }, { "date": "2026-04-27T16:38:07.311559Z", "number": "12", "summary": "CVSS created." }, { "date": "2026-04-27T16:38:13.968381Z", "number": "13", "summary": "NCSC Score updated." }, { "date": "2026-04-28T22:13:01.045037Z", "number": "14", "summary": "Products created (2).| Product Identifiers created (2)." }, { "date": "2026-04-28T22:13:03.315294Z", "number": "15", "summary": "NCSC Score updated." }, { "date": "2026-04-29T08:13:28.151340Z", "number": "16", "summary": "Source connected.| CVE status created. (valid)" }, { "date": "2026-04-29T15:49:07.903116Z", "number": "17", "summary": "EPSS updated." }, { "date": "2026-04-29T15:49:12.176735Z", "number": "18", "summary": "NCSC Score updated." } ], "status": "interim", "version": "18" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:semver/3.0.0|<4.14.6", "product": { "name": "vers:semver/3.0.0|<4.14.6", "product_id": "CSAFPID-6244636" } }, { "category": "product_version_range", "name": "vers:semver/4.15.0|<4.18.1", "product": { "name": "vers:semver/4.15.0|<4.18.1", "product_id": "CSAFPID-6244637" } } ], "category": "product_name", "name": "Apache Camel" } ], "category": "vendor", "name": "Apache Software Foundation" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/<4.14.6", "product": { "name": "vers:unknown/<4.14.6", "product_id": "CSAFPID-6244702" } }, { "category": "product_version_range", "name": "vers:unknown/<4.18.1", "product": { "name": "vers:unknown/<4.18.1", "product_id": "CSAFPID-6244701" } }, { "category": "product_version_range", "name": "vers:unknown/>=3.0.0|<4.14.6", "product": { "name": "vers:unknown/>=3.0.0|<4.14.6", "product_id": "CSAFPID-6252315", "product_identification_helper": { "cpe": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=4.15.0|<4.18.1", "product": { "name": "vers:unknown/>=4.15.0|<4.18.1", "product_id": "CSAFPID-6252316", "product_identification_helper": { "cpe": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*" } } } ], "category": "product_name", "name": "Camel" } ], "category": "vendor", "name": "Apache" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-33454", "cwe": { "id": "CWE-502", "name": "Deserialization of Untrusted Data" }, "notes": [ { "category": "description", "text": "The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\\\"imap://...\\\") or from(\\\"pop3://...\\\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).\n\nThis issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.\n\nUsers are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33454.json" }, { "category": "description", "text": "The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\\\"imap://...\\\") or from(\\\"pop3://...\\\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).\n\nThis issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.\n\nUsers are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33454" }, { "category": "other", "text": "0.00164", "title": "EPSS" }, { "category": "other", "text": "5.3", "title": "NCSC Score" }, { "category": "other", "text": "There is product data available from source Certbundde", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "Is related to a product by vendor Apache, The value of the most recent EPSS score, Is related to CWE-502 (Deserialization of Untrusted Data)", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-6244636", "CSAFPID-6244637", "CSAFPID-6244701", "CSAFPID-6244702", "CSAFPID-6252315", "CSAFPID-6252316" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33454.json" }, { "category": "external", "summary": "Source - certbundde", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-1271.json" }, { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-33454" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - ncscclear", "url": "https://advisories.ncsc.nl/advisory?id=NCSC-2026-0129" }, { "category": "external", "summary": "Reference - certbundde; cveprojectv5; nvd", "url": "https://camel.apache.org/security/CVE-2026-33454.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-1271.json" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-1271" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-27172.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40022.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40048.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40453.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40473.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40858.html" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://camel.apache.org/security/CVE-2026-40860.html" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L", "baseScore": 9.4, "baseSeverity": "CRITICAL" }, "products": [ "CSAFPID-6244636", "CSAFPID-6244637", "CSAFPID-6244701", "CSAFPID-6244702", "CSAFPID-6252315", "CSAFPID-6252316" ] } ], "title": "CVE-2026-33454" } ] }