Addressable, a Ruby URI alternative library, has a vulnerability in versions from 2.0.0 up to but not including 2.9.1 where its IDNA.to_unicode method improperly handles Unicode encoding. This allows decoding of Punycode labels containing bidirectional controls, zero-width characters, and other ignorable format characters, leading to visually reordered or indistinguishable hostnames in display_uri. The issue is fixed in version 2.9.1.
CVE-2026-62374 affects the @sd-jwt/core JavaScript library used for Selective Disclosure JWTs. Versions 0.19.0 and earlier of @sd-jwt/decode, also used by @sd-jwt/core, silently drop tampered or malformed Disclosures without rejecting them as required by RFC 9901. This silent claim reduction can lead to authorization decisions based on incomplete claim sets without error. The issue is fixed in @sd-jwt/core version 0.20.0.
CVE-2026-110687 is a vulnerability in Cpanel::JSON::XS versions from 4.43 up to but not including 4.80 for Perl. It involves improper handling of Unicode encoding during canonical encoding in the utf16_cmp function, causing misordering of byte-string keys. This results in inconsistent canonical JSON documents across processes.
CVE-2026-110674 is a type confusion vulnerability in Cpanel::JSON::XS for Perl versions from 4.33 up to but not including 4.80. The flaw arises when decoding JSON with relaxed parsing options that allow bare keys containing non-ASCII bytes, combined with the dupkeys_as_arrayref setting. This causes duplicate keys to bypass duplicate-key checks and leads to improper handling of repeated keys, resulting in type confusion. An attacker can craft malicious JSON input that causes the process to crash or dereference arbitrary memory addresses.
CVE-2026-89074 is a high-severity vulnerability in Progress MOVEit Transfer involving improper handling of Unicode encoding. It affects versions before 2025.1.6 and versions from 2026.0.0 up to but not including 2026.0.4. The vulnerability can lead to high impact on confidentiality, integrity, and availability. No specific patch links are provided in the data, and no known exploits are reported in the wild.
CVE-2026-105241 is a medium severity vulnerability in Apache log4net affecting versions from 1.2.9 up to but not including 3.5.0. It involves improper handling of Unicode encoding in the SmtpPickupDirAppender component. Specifically, when the mail file writer encounters content it cannot encode, such as an unpaired UTF-16 surrogate, it throws an error causing all buffered events in the batch to be discarded and potentially leaving a truncated mail file in the pickup directory. This can allow an attacker who controls log message content to suppress logging of other events. The issue is fixed in version 3.5.0.
Net::Whois::Raw versions before 2.99044 for Perl include a pwhois command-line tool that incorrectly handles Unicode domain names. The tool encodes non-ASCII labels using Net::IDN::Punycode but skips important IDNA mapping and normalization steps, causing incorrect domain queries for certain Unicode labels. The library modules themselves are not affected.
An improper authorization vulnerability in Fireware OS's Access Portal reverse proxy allows an authenticated, low-privileged Access Portal user to access other web applications they are not authorized for by sending a specially crafted request for a different resource which they are authorized to access.
CVE-2026-81869 is a medium severity vulnerability in the OpenTelemetry Go SDK trace package that allows bypass of the configured attribute value length limit for string attributes containing the Unicode replacement character U+FFFD. This flaw causes oversized attacker-controlled attribute values to be stored untruncated, weakening memory and denial-of-service protections. The vulnerability requires deployments with attribute value length limits enabled and attacker-controlled data recorded into span attributes. There is no indication of confidentiality or integrity impact.
HashiCorp go-slug versions 0.4.0 through 0.18.2 contain a vulnerability where improper handling of Unicode normalization during path matching can allow a local attacker to bypass .terraformignore exclusions. This may result in sensitive files being included in Terraform slug uploads.
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.
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**.
Caddy is an extensible server platform that uses TLS by default. From 2.7.0 until 2.11.3, the FastCGI transport's splitPos() in modules/caddyhttp/reverseproxy/fastcgi/fastcgi.go misuses golang.org/x/text/search with search.IgnoreCase when the request path contains a non-ASCII byte. Two distinct flaws in that fallback let an attacker mislead Caddy's FastCGI splitting into treating a non-.php (or other configured split_path extension) file as a script. In any deployment where the attacker can place content into a file served via FastCGI (uploads, file storage, etc.), this can be escalated to remote code execution by crafting a URL whose path triggers either flaw. This vulnerability is fixed in 2.11.3.
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.14, Deno's permission system enforces filesystem and execution restrictions by comparing the requested path against the path supplied to --deny-read, --deny-write, --deny-run, or --deny-ffi. On macOS, that comparison was done at the raw-byte level while the APFS filesystem treats different Unicode spellings of the same name as the same file. That means a program could reach a denied path by spelling it differently than the deny rule. This vulnerability is fixed in 2.7.14.
FrankenPHP is a modern application server for PHP. From version 1.11.2 to before version 1.12.3, the splitPos() function in cgi.go misuses golang.org/x/text/search with search.IgnoreCase when the request path contains a non-ASCII byte. Two distinct flaws in that fallback let an attacker mislead FrankenPHP into treating a non-.php file as a .php script. In any deployment where the attacker can place content into a file served by FrankenPHP (uploads, file storage, etc.), this can be escalated to remote code execution by crafting a URL whose path triggers either flaw. This issue has been patched in version 1.12.3.
SQLite 'sqldiff.exe' does not securely handle the way the Microsoft Windows C runtime converts Unicode characters to ANSI codepages. An attacker could use the '-L' option to load an arbitrary DLL with a crafted command line argument string that results in command line file arguments being misinterpreted as command line options. Fixed on or around 2025-12-26.
protobuf.js versions prior to 7.5.6 and between 8.0.0 and 8.0.2 contain a vulnerability in their UTF-8 decoding implementation. The minimal UTF-8 decoder accepted overlong UTF-8 byte sequences and decoded them to canonical characters instead of replacing them. This behavior may allow an attacker to bypass application-level checks that inspect raw bytes before protobuf string decoding.
Text::Minify::XS versions from 0.3.0 before 0.7.8 for Perl have a heap overflow when processing some malformed UTF-8 characters.
The minify functions mishandled some malformed UTF-8 characters, leading to heap corruption.
Note that the minify_utf8 function is an alias for minify.
A logic error in the split utility of uutils coreutils causes the corruption of output filenames when provided with non-UTF-8 prefix or suffix inputs. The implementation utilizes to_string_lossy() when constructing chunk filenames, which automatically rewrites invalid byte sequences into the UTF-8 replacement character (U+FFFD). This behavior diverges from GNU split, which preserves raw pathname bytes intact. In environments utilizing non-UTF-8 encodings, this vulnerability leads to the creation of files with incorrect names, potentially causing filename collisions, broken automation, or the misdirection of output data.