Fedora Account System
Red Hat Associate
Red Hat Customer
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:30853 https://access.redhat.com/errata/RHSA-2026:30853
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:30854 https://access.redhat.com/errata/RHSA-2026:30854
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:30855 https://access.redhat.com/errata/RHSA-2026:30855
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:34357 https://access.redhat.com/errata/RHSA-2026:34357
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:34359 https://access.redhat.com/errata/RHSA-2026:34359
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:35827 https://access.redhat.com/errata/RHSA-2026:35827
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:35828 https://access.redhat.com/errata/RHSA-2026:35828
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:35826 https://access.redhat.com/errata/RHSA-2026:35826
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:35831 https://access.redhat.com/errata/RHSA-2026:35831
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:35830 https://access.redhat.com/errata/RHSA-2026:35830
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:35829 https://access.redhat.com/errata/RHSA-2026:35829
This issue has been addressed in the following products: Red Hat OpenShift Container Platform 4.22 Via RHSA-2026:34789 https://access.redhat.com/errata/RHSA-2026:34789
This issue has been addressed in the following products: RHEM 1.0 for RHEL 9 Via RHSA-2026:36796 https://access.redhat.com/errata/RHSA-2026:36796
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:37436 https://access.redhat.com/errata/RHSA-2026:37436
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:37435 https://access.redhat.com/errata/RHSA-2026:37435
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:38995 https://access.redhat.com/errata/RHSA-2026:38995
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:39005 https://access.redhat.com/errata/RHSA-2026:39005
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:39573 https://access.redhat.com/errata/RHSA-2026:39573
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:39879 https://access.redhat.com/errata/RHSA-2026:39879
This issue has been addressed in the following products: RHEM 1.1 for RHEL 10 RHEM 1.1 for RHEL 9 Via RHSA-2026:41019 https://access.redhat.com/errata/RHSA-2026:41019