Japanese business media service NewsPicks on November 18, 2026 (JST) released a report on its investigation into the personal data breach it first disclosed in October. The company says a third party gained unauthorized access by exploiting a vulnerability in Metabase, a BI tool (software for visualizing and analyzing business data) it used to aggregate and analyze data. The number of affected records has now been finalized, with the largest category, partial credit card information, totaling 361,598.

The Entry Point Was a SQL Injection Flaw Exploitable Before Login

According to the company, the attacker used a SQL injection vulnerability in Metabase (CVE-2026-72898) that could be exploited without logging in. The flaw let the attacker bypass multi-factor authentication, impersonate an administrator, and create an API key with admin privileges. The attacker then pulled data from databases connected to Metabase, the company says.

NewsPicks explains that because the vulnerability allowed the application's authentication itself to be bypassed, multi-factor authentication and access controls were both rendered ineffective at once. The unauthorized access lasted from August 10 to September 28, 2026, and came from seven IP addresses, including some outside Japan, according to the company.

The Data Was Already Gone Before the Patch Was Applied

Metabase released fixed versions on August 6 and urged self-hosted users to upgrade immediately. According to Metabase's official blog, the flaw was a so-called zero-day, already being exploited before it was disclosed. The GitHub security advisory rates it at 10.0, the maximum CVSS v3.1 base score.

NewsPicks says the attack began four days after the disclosure, before a CVE number had been assigned. The company updated Metabase to a fixed version six days (three business days) after the disclosure, by which point personal data had already been taken. Even after the update, the company says, intermittent access continued until September 28 using API keys and other means the attacker had created.

An External Alert Led to the Discovery

The unauthorized access came to light on October 8. NewsPicks says it was discovered through an internal investigation prompted by an alert from an outside organization. On the same day, October 8, JPCERT/CC (Japan Computer Emergency Response Team Coordination Center) issued an alert on a string of unauthorized access incidents at organizations in Japan, which covered cases exploiting this Metabase vulnerability and listed suspicious source IP addresses.

The company says it had been keeping Metabase activity logs but was not continuously monitoring them for anomalies such as bulk data retrieval. It also cites as an aggravating factor the wide range of personal data visible with admin privileges, which even included some information on customers who had already canceled their accounts.

Affected Records Fell From the Second Report's Estimate

The finalized figures are shown in the table below. The company says the numbers dropped from the maximum estimates in its second report on October 9 after closer review, but the categories of leaked data have not changed.

ItemRecords
Partial credit card information (cardholder name, expiration date, last 3 or 4 digits of the number)361,598
Email addresses322,531
Job title at affiliated organization (7 categories)272,392
Affiliation (employer, etc.)64,572
Names58,754
Shipping addresses and recipient names30,906
Phone numbers of affiliated organizations28,013
Dates of birth27,194

Full card numbers are managed by the payment processor and are not stored by NewsPicks. The company also does not store security codes, and login passwords were not among the data taken, it says. As countermeasures, NewsPicks says it now requires network-level authentication to access Metabase and has reduced data access privileges to the minimum necessary.

Details are available in NewsPicks' investigation report, and information on the vulnerability can be found in Metabase's security update and JPCERT/CC's alert.

A Lesson That MFA Alone Is Not Enough

What stands out to us is that multi-factor authentication was meaningless once a vulnerability sitting in front of the authentication step was exploited. Internal analytics tools likely tend to lag behind public-facing services when it comes to updates and monitoring. Updating within three business days of a fix being released is not a slow response, yet the attack still came first.

That said, the direction for countermeasures is clear: limit the data visible from analytics tools to what is necessary, don't keep information that is no longer needed, and constantly watch for activity such as bulk retrieval. Any organization running BI tools internally, not just Metabase, should treat this as a prompt to review its own setup.

Summary

The NewsPicks data breach was caused by attackers exploiting a zero-day vulnerability in the BI tool Metabase and bypassing multi-factor authentication. While full card numbers and passwords were not leaked, names, email addresses, employers, and other data were exposed, so users should watch out for suspicious emails impersonating the company. Organizations self-hosting Metabase should not only update to a fixed version but also check that no suspicious API keys or admin accounts remain.