What is CVE-2026-46457?

CVE-2026-46457 is a high-severity improper input validation vulnerability in org.apache.camel:camel-nats (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2026-46457?

CVE-2026-46457 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.camel:camel-nats are affected by CVE-2026-46457?

org.apache.camel:camel-nats (maven) versions >= 4.0.0, < 4.14.8 is affected.

Is there a fix for CVE-2026-46457?

Yes. CVE-2026-46457 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Is CVE-2026-46457 exploitable, and should I be worried?

Whether CVE-2026-46457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-46457 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-46457 in org.apache.camel:camel-nats

Q: How severe is CVE-2026-46457?

CVE-2026-46457 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.camel:camel-nats are affected by CVE-2026-46457?

org.apache.camel:camel-nats (maven) versions >= 4.0.0, < 4.14.8 is affected.

Q: Is there a fix for CVE-2026-46457?

Yes. CVE-2026-46457 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Q: Is CVE-2026-46457 exploitable, and should I be worried?

Whether CVE-2026-46457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-46457 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-46457?

Upgrade: org.apache.camel:camel-nats to 4.14.8 or later, org.apache.camel:camel-nats to 4.18.3 or later, org.apache.camel:camel-nats to 4.21.0 or later.

Summary

Apache Camel-NATS: Inbound NATS message headers are mapped into the Exchange without a configured HeaderFilterStrategy, allowing a client that can publish to the subject to inject Camel control headers

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.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-46457 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.8, 4.18.3, 4.21.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.camel:camel-nats (>= 4.0.0, < 4.14.8) org.apache.camel:camel-nats (>= 4.15.0, < 4.18.3) org.apache.camel:camel-nats (>= 4.19.0, < 4.21.0)

Security releases

org.apache.camel:camel-nats → 4.14.8 (maven) org.apache.camel:camel-nats → 4.18.3 (maven) org.apache.camel:camel-nats → 4.21.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-nats to 4.14.8 or later; org.apache.camel:camel-nats to 4.18.3 or later; org.apache.camel:camel-nats to 4.21.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-46457? CVE-2026-46457 is a high-severity improper input validation vulnerability in org.apache.camel:camel-nats (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2026-46457? CVE-2026-46457 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.camel:camel-nats are affected by CVE-2026-46457? org.apache.camel:camel-nats (maven) versions >= 4.0.0, < 4.14.8 is affected.
Is there a fix for CVE-2026-46457? Yes. CVE-2026-46457 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.
Is CVE-2026-46457 exploitable, and should I be worried? Whether CVE-2026-46457 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-46457 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-46457?
- Upgrade org.apache.camel:camel-nats to 4.14.8 or later
- Upgrade org.apache.camel:camel-nats to 4.18.3 or later
- Upgrade org.apache.camel:camel-nats to 4.21.0 or later