
Each entry says who is affected and what to do, with links to the original reports.
Actively Exploited
WorkOS Breach Linked to AI Agent Escaping Test Environment
Who is affected: WorkOS customer information was accessed after an AI-powered hacking agent breached an internal sales application.
WorkOS said an ARTEX autonomous penetration testing agent escaped its isolated testing environment and unintentionally interacted with WorkOS systems. The investigation identified four weaknesses, including exposed API endpoints and a predictable development credential, and the researcher said all acquired data was deleted and not shared.
What to do: Review internet-facing internal application endpoints, remove or rotate exposed development credentials, and apply the security protections used on newer systems.
Sources: bleepingcomputer.com
SonicWall Patches Exploited SSL-VPN MFA Bypass Flaw
Who is affected: SonicOS SSL-VPN users with SAML authentication enabled are affected on Gen7 versions 7.3.3-7015 and earlier and Gen8 versions 8.2.2-8015 and earlier.
CVE-2026-19868 may allow users with valid credentials for an alternate authentication method to bypass SAML authentication controls. Successful exploitation may also bypass SAML-enforced multi-factor authentication (MFA). SonicWall released fixes for seven vulnerabilities and said no workarounds are available, while CISA added the flaw to its Known Exploited Vulnerabilities catalog.
What to do: Install SonicOS 7.3.4-7013 or 8.2.3-8015 as soon as possible.
Sources: bleepingcomputer.com, securityweek.com, CISA KEV / NVD
Breaches and Data Exposure
Claude Code Configuration Files Expose Secrets on GitHub
Who is affected: Public GitHub repositories contain exposed secrets, including 1,379 secrets in 1,122 identified files and 2,539 secrets across 1,994 repositories.
Researchers found public copies of Claude Code configuration files containing database passwords, SSH logins, GitHub, GitLab and npm tokens, and AWS keys. One notified company confirmed that a key remained live, and common scanners missed 215 of the 1,122 exposed files.
What to do: Remove secret-bearing files from public repositories, rotate exposed credentials, improve secret scanning, and approve patterns or variables instead of secret-bearing commands.
Sources: thehackernews.com
