Alerts This Week
Warning Icon 1 424
Alerts This Week
Warning Icon 1 424

Gentoo Asterisk High Code Execution Risks GLSA-202601-04

gentoo
Calendar Grey January 26, 2026
Dist Gentoo Esm H88
Critical vulnerabilities in Asterisk can lead to arbitrary code execution, requiring urgent updates for Gentoo Linux.
Multiple vulnerabilities have been discovered in Asterisk, the worst of which can lead to arbitrary code execution.

Summary

Multiple vulnerabilities have been discovered in Asterisk. Please review the CVE identifiers referenced below for details.

Resolution

# emerge --sync # emerge --ask --oneshot --verbose ">=net-misc/asterisk-18.26.3"

References

[ 1 ] CVE-2025-1131 https://nvd.nist.gov/vuln/detail/CVE-2025-1131 [ 2 ] CVE-2025-49832 https://nvd.nist.gov/vuln/detail/CVE-2025-49832 [ 3 ] CVE-2025-57767 https://nvd.nist.gov/vuln/detail/CVE-2025-57767 [ 4 ] GHSA-64qc-9x89-rx5j [ 5 ] GHSA-mrq5-74j5-f5cr [ 6 ] GHSA-v9q8-9j8m-5xwp

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202601-04
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
critical
Lowest
Low
Medium
High
Critical

Severity: High
Title: Asterisk: Multiple Vulnerabilities
Date: January 26, 2026
Bugs: #960930
ID: 202601-04

Synopsis

Multiple vulnerabilities have been discovered in Asterisk, the worst of which can lead to arbitrary code execution.

Background

Asterisk is an open source telephony engine and toolkit.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected ----------------- ------------ ------------ net-misc/asterisk < 18.26.3 >= 18.26.3

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here