Monthly
One-click account takeover in Telegram Desktop before 7.2.9, where the Core::Sandbox inter-process communication layer fails to neutralize the semicolon record separator in URLs delivered through tg:// links. An attacker who gets a victim to open a crafted tg:// link can smuggle an extra OPEN: record into the IPC stream; that record is dispatched to the interpret: scheme handler, which uploads attacker-chosen local files - most damagingly the tdata session keys - to an attacker-controlled channel, giving full control of the victim's Telegram account. The issue is unauthenticated and needs no non-default configuration (CVSS PR:N, default install); the sole prerequisite is passive user interaction, namely opening the attacker-supplied link, and publicly available exploit code exists. CISA KEV does not list this issue as confirmed actively exploited.
SNMP trap injection against Zabbix's bundled Perl trap receiver script allows a party that can deliver traps accepted by that receiver to forge a record against a different host, corrupting the integrity of collected monitoring data with no confidentiality or availability impact. The root cause is a failure to neutralize the ZBXTRAP record delimiter in CWE-143 terms, and only deployments that ingest traps through the shipped Perl script (typically wired into snmptrapd) are exposed. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the independent assessment rates this as a moderate, low-priority integrity issue (CVSS 3.1 5.3) rather than an urgent threat.
One-click account takeover in Telegram Desktop before 7.2.9, where the Core::Sandbox inter-process communication layer fails to neutralize the semicolon record separator in URLs delivered through tg:// links. An attacker who gets a victim to open a crafted tg:// link can smuggle an extra OPEN: record into the IPC stream; that record is dispatched to the interpret: scheme handler, which uploads attacker-chosen local files - most damagingly the tdata session keys - to an attacker-controlled channel, giving full control of the victim's Telegram account. The issue is unauthenticated and needs no non-default configuration (CVSS PR:N, default install); the sole prerequisite is passive user interaction, namely opening the attacker-supplied link, and publicly available exploit code exists. CISA KEV does not list this issue as confirmed actively exploited.
SNMP trap injection against Zabbix's bundled Perl trap receiver script allows a party that can deliver traps accepted by that receiver to forge a record against a different host, corrupting the integrity of collected monitoring data with no confidentiality or availability impact. The root cause is a failure to neutralize the ZBXTRAP record delimiter in CWE-143 terms, and only deployments that ingest traps through the shipped Perl script (typically wired into snmptrapd) are exposed. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the independent assessment rates this as a moderate, low-priority integrity issue (CVSS 3.1 5.3) rather than an urgent threat.