CWE-173— 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.— MITRE CWE catalog
5 active CVEs classified under this weakness category. Sourced from NVD, GHSA, and vendor advisories. Full definition on MITRE →
CVEs classified under CWE-173page 1 of 1
- CVE-2023-26302LOWCVSS 3.3EG 3.32023-02-22
Denial of service could be caused to the command line interface of markdown-it-py, before v2.2.0, if an attacker was allowed to use invalid UTF-8 characters as input.
- CVE-2023-26303LOWCVSS 3.3EG 3.32023-02-23
Denial of service could be caused to markdown-it-py, before v2.2.0, if an attacker was allowed to force null assertions with specially crafted input.
- CVE-2024-54158LOWCVSS 3.5EG 3.52024-12-04
In JetBrains YouTrack before 2024.3.52635 potential spoofing attack was possible via lack of Punycode encoding
- CVE-2026-10050CRITICALCVSS 9.1EG 9.12026-07-22
In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode the password as bytes. This was done because the initial specification for HTTP did not specify explicitly a charset, and it was assumed to be I…
- CVE-2026-19611HIGHCVSS 7.4EG 7.42026-08-20
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 …
Map vulnerabilities like CWE-173 to your infrastructure
EchelonGraph correlates every CVE — across CWE-173 and 150+ other weakness categories — against the assets you actually run. See blast radius, fix versions, and remediation steps in one graph.
Start Free Scan →