MeridianMeridian

Snowflake GitHub Actions Workflow Flaw Enabled Command Injection and Jira Token Theft

A vulnerability in Snowflake's GitHub Actions workflow in the snowflakedb/snowflake-connector-net repository allowed any user to execute arbitrary commands on a runner by creating a specially crafted issue in a public repository. The flaw stemmed from unsanitized insertion of issue titles and content directly into shell commands, combined with a failed access control check that relied on a non-existent pull request property during issue events. During authorized testing, an autonomous security agent exploited the issue to extract a Jira API token from the pipeline environment variables. This credential granted read access to internal engineering, security compliance, and bug bounty projects. The vulnerability was active from June 18 to June 23, 2026. Snowflake patched the workflow on the day the report was received and rotated the compromised token the following day. The vulnerable code appeared in a pull request that involved GitHub Copilot, though available history does not confirm the AI generated the insecure lines.

BoletimSecTranslated from Portuguese

Read at source

A vulnerability in a GitHub Actions workflow at Snowflake allowed any unauthenticated user to execute arbitrary commands on a runner simply by opening a specially crafted issue in a public repository.

The flaw resided in the snowflakedb/snowflake-connector-net repository. Issue titles and bodies were passed directly into shell commands without proper sanitization, creating a classic command-injection vector. An intended access-control check also failed because it referenced a pull-request property that does not exist in issue events, allowing ordinary users to bypass the restriction.

During authorized testing, an autonomous security agent exploited the weakness and retrieved a Jira API token stored in the workflow’s environment variables. The token provided read access to internal projects covering engineering, security compliance, and bug-bounty programs—information that could support further attack stages.

The vulnerable workflow remained active between 18 and 23 June 2026. Snowflake fixed the code on the same day the report was received and replaced the exposed token the following day. The affected code had been introduced in a pull request that included participation from GitHub Copilot, although the commit history does not prove the AI generated the insecure lines.

GitHub CopilotJiraSnowflakesnowflake-connector-net
ShareXFacebookLinkedInReddit
Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulnerabilities & Exploits

Telegram for Android Patches Voice Call Vulnerability Enabling Code Execution
Vulnerabilities & Exploits

Telegram for Android Patches Voice Call Vulnerability Enabling Code Execution

Security researchers at NebuSec disclosed a vulnerability in Telegram for Android that allowed remote code execution after a victim answered a voice call. The flaw affected versions from 8.6.2 through 12.10.3 and was fixed in release 12.10.4 at the end of September. The issue stemmed from improper handling of MediaState service messages that carry microphone, camera, and video rotation data during calls. When a required field was missing, the application accessed invalid memory. NebuSec discovered the bug using its Code Security product running on a GPT-5.4 model and confirmed exploitation on ARM64 Android devices for personal calls. A demonstration showed the string “HACKED BY NEBUSEC” appearing roughly 30 seconds after the call was accepted. The vulnerability is unrelated to the earlier animated-sticker attack vector.

AntiMalwareOct 29, 2026Translated from Russian

Yandex Patches Millions of Stations After eMudhra Certificate Keys Compromised
Vulnerabilities & Exploits

Yandex Patches Millions of Stations After eMudhra Certificate Keys Compromised

Yandex has automatically deployed security updates to millions of its smart speakers and partner televisions running YaOS between October 21 and 23. The patches address compromised intermediate certificates issued by eMudhra whose private keys consisted of trivial values from 1 to 255. Attackers who obtained these keys could generate fraudulent certificates and perform man-in-the-middle attacks against device HTTPS traffic. Enthusiasts demonstrated that local network control combined with the certificates allowed replacement of server configuration, activation of ADB, and acquisition of root access on the devices. The update removes trust in the affected certificates, overwrites compromised system files, and disables the debug interface. A factory reset restores the vulnerable firmware, so Yandex advises against resets without a compelling reason.

AntiMalwareOct 29, 2026Translated from Russian

Cisco ASA and FTD Face DoS Vulnerability in SSL VPN Already Exploited in the Wild
Vulnerabilities & Exploits

Cisco ASA and FTD Face DoS Vulnerability in SSL VPN Already Exploited in the Wild

Cisco Systems has disclosed a denial-of-service vulnerability affecting its Cisco Secure Firewall ASA and Cisco Secure Firewall FTD products. The flaw, tracked as CVE-2026-76418, resides in the SSL VPN remote access feature and carries a CVSS v3.1 base score of 8.6, rated High severity. Exploitation occurs when secondary authentication is configured on tunnel groups, allowing an attacker to send a crafted request that forces a device reboot without requiring authentication. Cisco confirmed active exploitation of the issue in October 2026. Security updates addressing the vulnerability are now available for both affected product lines. The advisory recommends immediate application of the patches to prevent service disruption.

Security NEXTOct 29, 2026Translated from Japanese