Monday 16 November
Global

Your region, kept on this device.

Supabase

Company

Security timeline

  1. Vulnerability reported by Orca Security BlogOrca Research finds widespread critical flaws in AI-generated apps and packages
  2. Vulnerability reported by The Hacker NewsClaude Code approval option can save secrets to settings files that leak to public GitHub repositories

Recent news

Orca Security Blog· · High

Orca Research finds widespread critical flaws in AI-generated apps and packages

Orca Research Pod reports that 51% of organisations have adopted AI to build software and 81% have critical vulnerabilities in AI packages. CVE-2025-48757 showed how one missing database policy in AI-generated projects exposed data across more than 170 production apps, and the post argues these shadow AI apps are often missed by existing scanning.

The Hacker News· · High

Claude Code approval option can save secrets to settings files that leak to public GitHub repositories

researchers found that 's "Yes, and don't ask again" option stores approved shell commands, including embedded passwords and API keys, in .claude/settings.local.json. Across 104,185 public copies of that file, they identified 2,539 distinct secrets in 1,994 repositories, affecting 63 organisations, including 379 database passwords, 122 Supabase service-role keys and 43 SSH logins. Standard scanners and TruffleHog missed 215 of the 1,122 affected local settings files.

Last updated 10 November 2026. Facts come from our own stories, NVD and CISA KEV, MITRE ATT&CK and Wikidata, each named beside the fact; the introduction, when there is one, is from Wikipedia. We never show company logos.

Report a mistake