Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7
Tag: misconfiguration (4 articles)Clear

Over 16,000 misconfigured Supabase databases expose personal data passwords and auth tokens

UpGuard found more than 16,000 misconfigured Supabase databases exposing readable tables with personally identifiable information, passwords, or authentication tokens, with a very small subset appearing to include credit card data. Supabase is an open-source PostgreSQL development platform, popular with developers using AI tools, which now account for more than 60 percent of newly created databases. UpGuard analyzed about 300,000 domains showing Supabase use and inferred exposed data types from table schemas. More than half of the exposed databases held PII, with a smaller subset exposing passwords and tokens. One US valet service alone exposed over 100,000 customer records, showing how missing access controls turn convenient backends into open data stores.

Check
Audit Supabase projects for tables readable without authentication, enable row-level security and proper policies, and rotate any exposed tokens or passwords.
Affected
Supabase projects deployed without row-level security or access policies expose their tables, leaking PII, credentials, and auth tokens to anyone who queries them.
Fix
Turn on row-level security, restrict anonymous access, review AI-generated backends for missing controls, and monitor for unauthorized table reads.

Surfshark VPN says a misconfigured test server let attackers reach build credentials

VPN provider Surfshark disclosed that attackers accessed an internal engineering test server that a configuration error had left reachable from the internet, along with a proxy server used for content optimization. Surfshark says the exposure was limited to a non-production environment and included service configurations, build-related credentials, system binaries, and portions of code history, but did not reach customer data, VPN traffic, encryption keys, or production systems. The company detected the activity on August 31, contained it by September 2, rotated credentials, revoked tokens, and completed remediation within days. It is a reminder that misconfigured internet-exposed test environments remain a common and avoidable breach path, even at security-focused companies.

Check
Inventory internet-facing assets for exposed test, staging, and engineering servers, remove public access to non-production systems, and rotate any build credentials or tokens that a test environment could expose.
Affected
Organizations with internal test or engineering servers unintentionally reachable from the internet; attackers can obtain build credentials, configurations, and source history, which can seed further compromise even when production data is untouched.
Fix
Keep non-production environments off the public internet, apply production-level access controls to test systems, store credentials in dedicated vaults rather than build environments, continuously scan your external attack surface, and rotate secrets.

Vatican prayer app left personal data of 700,000 users exposed

Researchers found that an official Vatican prayer app exposed the personal information of more than 700,000 users worldwide through an insecure configuration. The exposed data included details that can identify individuals and tie them to their use of the app. Faith and health apps are sensitive because the mere fact of using them can be revealing, and religious affiliation is a protected category in many jurisdictions, so even a modest data set carries outsized risk for the people in it. The exposure stemmed from the way the app's backend was set up rather than a sophisticated intrusion, a recurring pattern in mobile app data leaks where access controls are misconfigured.

Check
App developers should review backend access controls and confirm that user data stores require authentication and are not readable by anyone who can reach the endpoint.
Affected
More than 700,000 users of the Vatican prayer app whose personal information was exposed; because the data links people to a religious app, it is sensitive even where individual fields seem limited.
Fix
Developers should enforce authentication on all data endpoints, apply least privilege to backend stores, test for misconfiguration before release, and minimize the personal data collected by faith and health apps.

Pitney Bowes customer and employee data leaked publicly - 8.2 million email addresses plus internal records with employee job titles

Pitney Bowes customer and employee data was leaked publicly after the company refused to pay ShinyHunters' extortion demand. Have I Been Pwned added the breach yesterday with 8.2 million unique email addresses, plus names, phone numbers, and physical addresses. A subset includes Pitney Bowes employee records with job titles - a useful starter pack for highly-targeted phishing against named staff. The data came from a misconfigured Salesforce Experience Cloud 'Guest User' permission that let unauthenticated visitors query CRM records directly. ShinyHunters had posted Pitney Bowes on its leak site April 18 with a three-day deadline.

Check
If your organization uses Salesforce Experience Cloud, audit Guest User permissions today and remove read access from CRM objects that don't need to be public.
Affected
Pitney Bowes customers (8.2M email addresses, names, phones, addresses now public) and employees with job titles in the leak. Any organization running Salesforce Experience Cloud with default Guest User permissions has the same exposure - this is a configuration failure, not a Salesforce flaw.
Fix
Run Salesforce's Guest User Permissions report and tighten anything reading customer or contact data. Confirm no Experience Cloud public site exposes Account, Contact, Lead, or Case objects without a clear public-data reason. Pitney Bowes employees should treat 'CEO needs you to wire' messages with extra suspicion - your name and title are now public.