# CVE-2026-19611: Weak cryptography in Red Hat Build of Apache Camel 3.33.3.SP2

> Attackers can guess passwords more easily because Unicode normalization collapses fullwidth characters to ASCII, reducing the effective password keyspace.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-h79m-h3j4-r7qm

## What is CVE-2026-19611?

CVE-2026-19611 is a high-severity vulnerability in Red Hat Build of Apache Camel 3.33.3.SP2, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-173 (Improper Handling of Alternate Encoding)

## Which versions are affected by CVE-2026-19611?


## How do I fix CVE-2026-19611?

No fix has been published for CVE-2026-19611 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19611 being exploited?

There is no known exploitation of CVE-2026-19611 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19611 and fix it if it is affected.

What it is: CVE-2026-19611 is a high-severity vulnerability in Red Hat Build of Apache Camel 3.33.3.SP2, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19611 in the wild and no public exploit code.

Affected product: Red Hat Build of Apache Camel 3.33.3.SP2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19611/ (Markdown: https://insights.sbomify.com/CVE-2026-19611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19611
- OSV: https://osv.dev/vulnerability/CVE-2026-19611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19611/
Summaries are generated and may contain mistakes; the official description above is the record.