CVE Index中文
L4 · Septic Tank BlewRakuten Securities · data breach · test environmentrakuten-securities-test-data

Rakuten Securities reports possible customer-data theft from a test environment

Rakuten Securities reports possible exposure of detailed personal and financial data for up to 4.47 million accounts and identifiers for up to 11.25 million accounts. Password/PIN exposure and resulting unauthorized transactions are not confirmed. The company blocked access and is investigating.

Disclosed
Nov 17, 2026
Public disclosure date
Severity
Septic Tank Blew
No CVE: a breach, not a bug
Splash zone
Current and former Rakuten Securities accounts represented in the affected test-environment data; individual notices define exposure
Rakuten Securities · data breach · test environment
In the wild
Not applicable
Vendor reports intrusion; the entry method and extent of data theft remain unconfirmed.

What happened

Rakuten Securities says unauthorized access may have exposed data held in a test environment, including information about former customers. This is a vendor-confirmed incident with possible large-scale exposure of sensitive financial and personal data, which supports L4. It has not established that every listed record was stolen, identified an entry vulnerability or published a final root cause.

The notice lists two maximum account populations. Up to 4.47 million accounts may involve branch/customer codes, securities login IDs, names and kana names, birth dates, addresses, phone numbers, email, employer, withdrawal-bank details (institution, account number and holder), self-reported income and financial assets, assets by product and last login date. Up to 11.25 million accounts may involve branch/customer codes and securities login IDs. These login IDs differ from Rakuten IDs. The notice does not explain overlap between the two populations; do not add them into a unique-customer total.

The company has not confirmed exposure of login passwords, PINs or other information needed for transactions, or related unauthorized access or trading resulting from this incident. That does not remove phishing risks from exposed identifiers or personal information. It says it identified affected customers and will contact them individually; notification is not described as complete. Access blocking and corrections are containment steps, not independent verification that copied information has been recovered.

Crime-scene timeline

  1. Nov 11, 2026

    Investigation identifies a possible data outflow

    Rakuten Securities dates the suspected exposure of test-environment information to this day.

  2. Nov 16, 2026

    The company detects suspicious access and blocks the affected area

    It reports access blocking and corrections; the cause and detailed sequence remain under investigation.

  3. Nov 17, 2026

    Rakuten Securities publishes the affected data categories

    It has identified affected customers and plans individual notifications, with two upper-bound account counts.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.