cve.bz

CVE-2026-46457 apache camel: Improper Input Validation

7.5 highEPSS 0.7%Fix available

High (7.5) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-nats 4.14.8, 4.18.3, 4.21.0.

On this page
Improper Input Validation vulnerability in Apache Camel NATS component. The camel-nats component maps inbound NATS message headers into the Camel Exchange but defaulted its headerFilterStrategy to a bare new DefaultHeaderFilterStrategy() with no inbound rules configured (NatsConfiguration). With no inFilter, inFilterPattern or inFilterStartsWith set, DefaultHeaderFilterStrategy.applyFilterToExternalHeaders returns not filtered for every header name, so NatsConsumer copies every NATS message header - including Camel-internal control headers such as CamelHttpUri, CamelFileName or CamelSqlQuery - unmodified onto the Camel message. A client able to publish to the consumed NATS subject can therefore inject arbitrary Camel control headers that influence the behaviour of downstream producers in the route (for example redirecting an HTTP producer, changing a file name, or overriding a query); the injected headers also persist across internal direct, seda and vm hops. The concrete downstream impact depends on which producers the route uses. NATS message headers require NATS 2.2 or later, and the issue is reachable without credentials when the NATS server is configured without authentication (the NATS server default). 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. The fix makes camel-nats default to a dedicated NatsHeaderFilterStrategy that filters the Camel header namespace case-insensitively on inbound mapping, so client-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from inbound NATS messages before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), and enable authentication on the NATS server so that only trusted clients can publish to the consumed subject.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46457 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46457?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46457?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46457 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-46457

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-46457](https://cve.bz/cve/badge/CVE-2026-46457.svg)](https://cve.bz/cve/CVE-2026-46457)

HTML:

<a href="https://cve.bz/cve/CVE-2026-46457"><img src="https://cve.bz/cve/badge/CVE-2026-46457.svg" alt="CVE-2026-46457"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7v55-q9x3-83cjMavenorg.apache.camel:camel-nats>=4.0.0 <4.14.84.14.8
GHSA-7v55-q9x3-83cjMavenorg.apache.camel:camel-nats>=4.15.0 <4.18.34.18.3
GHSA-7v55-q9x3-83cjMavenorg.apache.camel:camel-nats>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This Important vulnerability in the Apache Camel NATS component allows an unauthenticated attacker to inject arbitrary Camel control headers into the message exchange. This is possible when the NATS server lacks authentication, enabling a client to manipulate downstream producer behavior, such as redirecting HTTP requests or altering file operations. The impact is significant due to the potential for unauthorized control over data flow within Camel routes.

Red Hat's mitigation

To reduce exposure, configure Apache Camel routes to filter out Camel control headers from incoming NATS messages before they are processed by any downstream producer. Additionally, enable authentication on the NATS server to restrict publishing access to trusted clients only.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16camelFixed 2026-09-24RHSA-2026:71675

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46457.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-46457 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-46457 — Apache Camel camel-nats inbound header injection (Camel control-header injection via a NATS publisher; Came…

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON