Поиск уязвимостей
Количество 18
Количество 18
GHSA-ch73-g8qv-r6r5
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-6791
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-6791
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-6791
When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-6791
Potential stack-based buffer clash during tilde expansion in wordexp
CVE-2026-6791
When expanding paths that begin with a tilde (~) followed by a usernam ...
RLSA-2026:76777
Moderate: glibc security update
ELSA-2026-76777
ELSA-2026-76777: glibc security update (MODERATE)
ELSA-2026-500586
ELSA-2026-500586: glibc security update (MODERATE)
RLSA-2026:76781
Moderate: glibc security, bug fix, and enhancement update
ELSA-2026-76781
ELSA-2026-76781: glibc security, bug fix, and enhancement update (MODERATE)
SUSE-SU-2026:4204-1
Security update for glibc
RLSA-2026:79281
Moderate: glibc security, bug fix, and enhancement update
ELSA-2026-79281
ELSA-2026-79281: glibc security, bug fix, and enhancement update (MODERATE)
ELSA-2026-500576
ELSA-2026-500576: glibc security update (MODERATE)
SUSE-SU-2026:4250-1
Security update for glibc
openSUSE-SU-2026:21968-1
Security update for glibc
SUSE-SU-2026:4591-1
Security update for glibc
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-ch73-g8qv-r6r5 When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash. | 0% Низкий | 3 месяца назад | ||
CVE-2026-6791 When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash. | 0% Низкий | 3 месяца назад | ||
CVE-2026-6791 When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash. | CVSS3: 5.9 | 0% Низкий | 3 месяца назад | |
CVE-2026-6791 When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash. | 0% Низкий | 3 месяца назад | ||
CVE-2026-6791 Potential stack-based buffer clash during tilde expansion in wordexp | 0% Низкий | 3 месяца назад | ||
CVE-2026-6791 When expanding paths that begin with a tilde (~) followed by a usernam ... | 0% Низкий | 3 месяца назад | ||
RLSA-2026:76777 Moderate: glibc security update | около 1 месяца назад | |||
ELSA-2026-76777 ELSA-2026-76777: glibc security update (MODERATE) | 15 дней назад | |||
ELSA-2026-500586 ELSA-2026-500586: glibc security update (MODERATE) | 9 дней назад | |||
RLSA-2026:76781 Moderate: glibc security, bug fix, and enhancement update | около 1 месяца назад | |||
ELSA-2026-76781 ELSA-2026-76781: glibc security, bug fix, and enhancement update (MODERATE) | 15 дней назад | |||
SUSE-SU-2026:4204-1 Security update for glibc | 2 месяца назад | |||
RLSA-2026:79281 Moderate: glibc security, bug fix, and enhancement update | около 1 месяца назад | |||
ELSA-2026-79281 ELSA-2026-79281: glibc security, bug fix, and enhancement update (MODERATE) | 16 дней назад | |||
ELSA-2026-500576 ELSA-2026-500576: glibc security update (MODERATE) | 14 дней назад | |||
SUSE-SU-2026:4250-1 Security update for glibc | 2 месяца назад | |||
openSUSE-SU-2026:21968-1 Security update for glibc | около 2 месяцев назад | |||
SUSE-SU-2026:4591-1 Security update for glibc | около 1 месяца назад |
Уязвимостей на страницу