Red Hat Build of Apache Camel 3.33.3.SP2: Improper Handling of Alternate Encoding
CVE-2026-19611 is a high-severity improper handling of alternate encoding vulnerability in Red Hat Build of Apache Camel 3.33.3.SP2 from Red Hat, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.03% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Build of Apache Camel 3.33.3.SP2 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (redhat.com).
Official description
A flaw was found in WildFly Elytron. Password hashing and verification normalize input with Unicode NFKC, which can collapse fullwidth characters to ASCII equivalents. A remote attacker can more easily guess affected passwords by using an ASCII-only dictionary against accounts whose passwords were intended to include those non-ASCII characters, leading to unauthorized access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Alternate Encoding
The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.
How developers prevent this class of flaw
- Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
More Improper Handling of Alternate Encoding vulnerabilities (CWE-173)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:69440
- access.redhat.com/errata/RHSA-2026:69470
- access.redhat.com/errata/RHSA-2026:70257
- access.redhat.com/errata/RHSA-2026:83612
- access.redhat.com/errata/RHSA-2026:95759
- access.redhat.com/errata/RHSA-2026:95760
- access.redhat.com/errata/RHSA-2026:95761
- access.redhat.com/errata/RHSA-2026:95762
- access.redhat.com/errata/RHSA-2026:95887
- access.redhat.com/security/cve/CVE-2026-19611
- bugzilla.redhat.com/show_bug.cgi?id=2514568
Other vulnerabilities in Red Hat Build of Apache Camel 3.33.3.SP2
- 8.2 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Handling of Alternate Encoding vulnerabilities
- 9.1 Critical severity
Spotted an error? Tell us.