CVE-2026-35375

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.

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.

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.

Un error de lógica en la utilidad ’split’ de uutils coreutils causa la corrupción de los nombres de archivo de salida cuando se le proporcionan entradas de prefijo o sufijo que no son UTF-8. La implementación utiliza to_string_lossy() al construir nombres de archivo de fragmentos, lo que reescribe automáticamente las secuencias de bytes inválidas en el carácter de reemplazo UTF-8 (U+FFFD). Este comportamiento difiere de GNU split, que preserva los bytes de la ruta de acceso sin procesar intactos. En entornos que utilizan codificaciones que no son UTF-8, esta vulnerabilidad conduce a la creación de archivos con nombres incorrectos, lo que podría causar colisiones de nombres de archivo, automatización rota o la redirección errónea de datos de salida.