30
30
30
30
30
30
30
30
30
30
30
30
45
30
30
30
30
30
30
30
30
45
Snowflake GitHub Actions Flaw Lets Crafted Issues Trigger Command Injection
Wiz disclosed a GitHub Actions workflow injection in Snowflake's snowflake-connector-net repo that exposed Jira API tokens; Snowflake patched the flaw.
Wiz disclosed a workflow injection flaw in Snowflake's snowflake-connector-net repository, where attacker-controlled GitHub issue fields were expanded directly into a shell run block. Wiz's Red Agent exploited it during authorized security testing, received an out-of-band runner callback and retrieved a Jira API token with read access to engineering, security compliance and bug bounty projects. Snowflake merged a fix on June 23, 2026, rotated the token and said its investigation found no evidence of unauthorized access. No CVE, CVSS score or KEV entry has been assigned for the issue.
45
Fake CVE-2023
A fake PoC for WinRAR RCE CVE-2023-40477 posted on GitHub actually deploys VenomRAT through a multi-step infection chain targeting researchers.
Four days after Zero Day Initiative publicly disclosed the WinRAR RCE vulnerability CVE-2023-40477 on August 17, 2023, an actor using the alias whalersplonk published a fake proof-of-concept on GitHub. The Python script actually repurposed public PoC code for GeoServer SQL injection CVE-2023-25157 and triggered an infection chain ending in VenomRAT. The README and an accompanying video lured users into running the script; the video drew over 100 plays. Unit 42 assesses the actor was opportunistic, targeting other miscreants adopting new vulnerabilities rather than researchers specifically.
40
30
30
45
35
30
30
30
30
30
30
30
45
50,000 Stripe Secrets Leaked in Public Code
Over 50,000 Stripe merchant API keys leaked via public code and logs; 659 merchant accounts' data offered on trading forum.
Ransomnews researchers identified over 50,000 unique Stripe merchant API keys exposed in public GitHub repositories, GitHub Actions logs, and misconfigured web servers. A dataset on a data-trading forum dated August 18, 2026 contained live keys for 659 merchant accounts plus roughly 35 GB of customer and payment data. Researchers demonstrated a leaked key enabled accessing customer lists, creating fraudulent payment links, and making test charges within 17 hours. Stripe itself was not compromised; over 3,000 misconfigured web servers revealed Stripe-related strings, with about 12% containing working keys.
60
35
30
30