CWE-176Variant

Improper Handling of Unicode Encoding

Draft in the CWE catalog · 28 CVEs mapped

28
CVEs mapped
6.4
Median CVSS
What it is

The product does not properly handle when an input contains Unicode encoding.

Recent examples
5.5cvss
CVE-2026-14978

CVE-2026-14978 - MEDIUM Severity Vulnerability

HashiCorp go-slug 0.4.0 through 0.18.2 could allow a local attacker to bypass .terraformignore exclusions and cause sensitive files to be included in Terraform slug uploads due to improper handling of Unicode normalization during path matching.

MEDIUMno explanation yet
0%
epss
6.1cvss
CVE-2026-59890

setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD) on macOS APFS/HFS+

setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. Prior to 83.0.0, FileList applied MANIFEST.in exclude, global-exclude, recursive-exclude, and prune directives by matching compiled glob patterns against on-disk file names without Unicode normalization, so on macOS APFS or HFS+ an NFD file name could bypass an NFC exclusion rule and be packed into a source distribution. This issue is fixed in version 83.0.0.

MEDIUMno explanation yet
0%
epss
6.5cvss
CVE-2026-48618

CVE-2026-48618 - MEDIUM Severity Vulnerability

A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

MEDIUMno explanation yet
3%
epss
The record
Technical detail
CWE ID
CWE-176
Abstraction
Variant
Structure
Simple
Status
Draft