Skip to main content
VulnerabilityPublished Updated

CVE-2026-19611: WildFly Elytron · CWE-173

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-19611· High 7.4

Not known to be exploited · CVSS 7.4 High : patch Red Hat Build of Apache Camel 3.33.3.SP2 soon.

Data as of 6 Nov 2026, 13:49 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Build of Apache Camel 3.33.3.SP2org.wildfly.security/wildfly-elytron-password-implAffected–Fixed in–
Red HatRed Hat Build of Debezium 3.6Affected–Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-containerAffected–Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-operator-bundle-containerAffected–Fixed in–
Red Hat build of Keycloak 26.4keycloak-rhel9-operator-containerAffected–Fixed in–
Red Hat build of Keycloak 26.6.8keycloak/rhbk-openshift-rhel9Affected–Fixed in–

AI-suggested

A security update fixing this vulnerability is available in Red Hat build of Quarkus version 3.33.3.SP2. Users should apply this update to remediate the issue. Since the vulnerability is fixed in this release, no additional mitigation steps are required beyond applying the official patch.

Description

A vulnerability in WildFly Elytron's password hashing and verification process causes input normalization using Unicode NFKC, which collapses fullwidth characters to ASCII equivalents. This reduces the effective password keyspace, allowing remote attackers to more easily guess passwords intended to include non-ASCII fullwidth characters by using ASCII-only dictionaries, potentially leading to unauthorized access.

References

Community reviews

Loading reviews…