A security researcher has disclosed a critical tenant isolation vulnerability in the AI meeting recorder tl;dv, exposing 181,874 meeting records and live conference IDs. The issue, discovered on January 28, 2026, remains unfixed and unacknowledged by the company's CTO for over six months, as of July 2026.
tl;dv, which records, transcribes, and summarizes Google Meet, Zoom, and Teams calls, authenticates users with a JWT exchanged for a Firebase token via gw.tldv.io/v1/users/firebase/token. The platform's Firestore database, at projects/lmi-store/databases/(default), contains a "meetings" collection with no tenant isolation. Any authenticated tl;dv user can query every meeting across all accounts.
Each meeting record includes the creator's email, conference ID, provider, recording status, and timestamps. Conference IDs for meetings in "recording" status are live, joinable calls. At any given time, roughly 1,000 meetings have status: recording.
The researcher joined a live Google Meet of the Malaysian Ministry of Education with 157 participants. They also joined a call with students from a major US university building a startup app; 21 people were in the call. The university students were screen-sharing, discussing prototypes, and setting up Supabase live.
The Scope of the Exposure
The vulnerable collection holds 181,874 meeting records, affecting 84,312 unique users across 35,003 email domains. Government meetings from 23 countries were exposed, including Brazil, Colombia, Peru, Ukraine, El Salvador, the Philippines, Chile, Indonesia, Mexico, the United States, Qatar, Malaysia, Uzbekistan, Sri Lanka, Haiti, South Africa, Jamaica, Honduras, Argentina, Thailand, Japan, Israel, and Belize.
University meetings from Berkeley, University of Tokyo, De La Salle, and Universidad Nacional de Colombia were also exposed. Mitsui-Soko had 484 meetings across four regional offices. Mitsui Fudosan, HubSpot, Confluent, Mekari, and AnyMind Group all had exposed meeting records.
The peak month was July 2025 with 43,209 meetings. The busiest time slot was Wednesday at 2pm UTC with 7,804 meetings. The researcher scraped 27,334 meeting IDs to check public status, finding over 1,000 meetings were public. Public meetings included PACTO Mata Atlântica, Ukraine's Ministry of Digital Transformation, a HubSpot sales call, Universidad Nacional de Colombia, and Chile's Cámara Verde. The researcher also found 715 invitee emails exposed across 228 domains.
PACTO Mata Atlântica, a Brazilian government conservation meeting, included participants from WWF, The Nature Conservancy, Conservation International, WRI, and São Paulo state government.
A Six-Month Silence
The disclosure timeline began on January 28, 2026, when the researcher messaged Raphael Allstadt, a tl;dv employee, on LinkedIn. Raphael responded within minutes: "thank you! can you report it to our CTO and we will look at it immediately?"
The researcher sent an email to the CTO. Raphael said "My CTO will come back to you." On January 29, the researcher followed up: "your cto hasnt reached out yet btw and its not fixed." On January 30, Raphael said "I am sure the team is reviewing it very very soon ❤️."
On February 14, the researcher followed up: "havent got an email and the vulnerability stilll works." Raphael said "He'll come back ☺️." On February 19, Raphael said "We're on it. It needs some time, but rest assured we're following through. For further communication, i'll recommend reaching out to our CTO."
The researcher noted: "I told him to maybe fix the vulnerability and not leave customers exposed. February 19th:" On March 6, the researcher followed up: "still not fixed." The message was seen by Raphael at 5:42 PM. No reply came. On July 22, the researcher followed up: "still not fixed..." No reply came.
The CTO never responded to any emails. The researcher emailed the CTO directly, and no response arrived in six months.
Compliance Claims Contradicted
tl;dv's security page claims SOC2 compliant, GDPR compliant, EU AI Act compliant, hosted in EU, AES-256 encryption. The page has six compliance badges. It states: "If you have discovered a privacy or security issue that we should address, please always let us know at [email protected]. Our security team will respond within 24 hours."
Stay ahead of the AI curve
The most important updates, news, and content — delivered weekly.
No spam. Unsubscribe anytime.
That promise is contradicted by the six-month silence. The researcher's emails were possibly too long and not viewed by the CTO.
Other Firestore collections, including users, chats, transcripts, clips, recordings, videos, notes, teams, and organizations, return 403 for unauthorized access. Only the "meetings" collection is misconfigured. The vulnerability is fixable with Firestore security rules, as done for other collections.
An attacker with a bot could join all ~1,000 live calls simultaneously. The lack of tenant isolation is a critical design flaw. The exposed conference IDs allow unauthorized access to live calls. The company's compliance badges are undermined by the vulnerability.
The World Cup Pick'em App
The researcher found https://worldcup.tldv.io, a FIFA World Cup 2026 prediction game. The game was built on Base44 for tl;dv employees. The internal squad name is "Too Long; Didn't Score."
The Player entity API has zero authentication. GET /api/entities/Player returns all player records. The API response contained 43 players, including 19 @tldv.io employees with full names and corporate emails exposed. Raphael Allstadt came in 2nd place with 298 points. His personal Gmail was in the API response.
Player #5 on the leaderboard is "Super Duper CEO," implied to be the tl;dv CEO. Prediction and Fixture entities are also wide open.
The internal app's lack of authentication is ironic given the company's core business. The researcher suggests putting auth on the World Cup app or taking it down. They also suggest responding to security researchers.
tl;dv microservices are named after pasta, including cappellini, carbonara, fusilli, pasta, penne, puttanesca-v0, and ravioli under tldv.io.
A Growing Concern
tl;dv has over 2 million users. The platform is backed by investors and endorsed by half of LinkedIn's sales influencer community. It records sales calls, job interviews, performance reviews, and internal strategy sessions.
The vulnerability remains open as of July 2026. The researcher's disclosure timeline spans from late January 2026 to July 2026. The company's response, or lack thereof, to security researchers is a major concern.
The World Cup Pick'em app is a "vibecoded" internal fun app. Its lack of authentication leaks the employee directory. The researcher found that the app's Player entity API returns all player records without any authentication.
The researcher's findings highlight a pattern of neglect. The Firestore database is still wide open. The CTO never responded. Raphael Allstadt gave vague reassurances and went silent. The vulnerability is fixable, but no fix has been applied.
The exposed data includes sensitive government and corporate meetings. The Malaysian Ministry of Education call had 157 participants. The US university call had 21 people. These are real, live meetings that anyone could join.
The researcher's analysis suggests the company's security posture is inadequate. The compliance badges are contradicted by the vulnerability. The internal app's lack of authentication is a separate issue. The company's response to the researcher is a major concern.