PLAID KARTE Unauthorized Access: Platform Shut Down, Customers Asked to Revoke Integration Keys

PLAID KARTE security advisory: platform shut down, revoke keys. High, no CVE. Not in CISA KEV.

Status: Contained, still offline, according to PLAID. PLAID said on 15 November 2026 at 10:37 JST (UTC+9) that new unauthorized access and ongoing leakage "have been stopped" (Rescana's translation from Japanese). As of its status update of 17 November at 15:52 JST (UTC+9), every KARTE function remains shut down with no restore date. No CVE has been assigned and no attribution has been published.

Executive Summary

KARTE is a customer experience (CX) platform from PLAID, Inc. (TSE Growth: 4165). Companies embed it in websites and apps to measure visitors and deliver messages and email. According to PLAID's status page, its notice of 13 November, its notice of 16 November and its Tokyo Stock Exchange disclosure:

  • In the early hours of 13 November 2026 JST (UTC+9), a third party exploited a server vulnerability, stole credentials and read data out of PLAID's databases. PLAID began shutting down all KARTE projects the same day.
  • PLAID has confirmed the leak of email addresses registered as KARTE accounts (accounts held by PLAID's client companies; PLAID gives a figure of 79,249 addresses), credentials that connect KARTE to external services (secret keys, access tokens and similar), and some customer data that client companies imported into KARTE, which may include personal information.
  • PLAID asks customers to revoke those integration credentials and warns of phishing emails impersonating PLAID sent to KARTE account addresses.
  • PLAID is contacting affected customer companies individually, reporting to Japan's Personal Information Protection Commission and consulting the police.

In Rescana's assessment, the third-party risk sits in the integrations: leaked keys can open the data stores and SaaS tools KARTE was connected to. The questions are: which suppliers use KARTE on sites or apps that touch your customers or data, and have they revoked and reissued the keys that connect it to other services?

What Happened

Dates and times below are as PLAID posted them, in JST (UTC+9). Quotations and summaries of PLAID's Japanese text are Rescana's translations.

How the intrusion happened (PLAID's 16 November notice). In the early hours of 13 November, a third party exploited a vulnerability in PLAID's servers, stole credentials used to connect to systems and databases, and read data out of databases and similar systems. It also used the stolen credentials to take over PLAID accounts and access the admin console. PLAID detected the access at 08:59 JST that day and invalidated the stolen credentials, among other steps. From around 14:27 JST it began stopping servers and switched all KARTE services to maintenance mode. Containment, including blocking traffic from the attack source, was complete by around 15:23 JST. PLAID says no new unauthorized access has been confirmed since.

Status page updates (incident "緊急メンテナンスのためKARTE全体のサービスを停止します", Rescana's translation: "Emergency maintenance: stopping the entire KARTE service"):

  • 13 November, 14:44. Emergency shutdown of KARTE for all projects.
  • 13 November, 23:35. PLAID had identified information that may have leaked and had emailed the affected customers.
  • 15 November, 10:37. Network isolation "is complete"; ongoing leakage "has been stopped".
  • 15 November, 16:01. PLAID began contacting affected customers at their registered fault and outage contact addresses and again asked customers to revoke integration secret keys and access tokens.
  • 16 November, 20:52. No major new findings; restore date undecided.
  • 17 November, 10:47. PLAID pointed to its 16 November notice for the leak scope confirmed so far, said it is also contacting customers individually, and said a restore date is still undecided. It said its next update would come around 16:00 JST.
  • 17 November, 15:52. PLAID said its investigation into the scope of the unauthorized access is progressing and that, for some of the data, it has begun working to identify the affected customers. It said it will start preparing to contact those customers in turn, beginning with those it has identified, that the restore date is still undecided, and that its next update would come around 21:00 JST.

What PLAID confirmed leaked (16 November notice):

  1. Email addresses registered as KARTE accounts, which PLAID groups under information about its client companies' accounts (ご利用企業のアカウントに関する情報), separately from the client companies' own customer data in item 3. PLAID's notice lists "KARTEのアカウントとして登録されているメールアドレス:79,249件" (Rescana's translation: "email addresses registered as KARTE accounts: 79,249").
  2. Credentials used to connect KARTE to external services (secret keys, access tokens and similar), for customer companies that had configured those integrations. Count still under investigation.
  3. Some of the data that customer companies imported into KARTE to use their own customer information there (for example membership data), including data imported through KARTE's "linked tables" (紐付けテーブル) function. Each company chooses the imported fields, so the data may include personal information. Count still under investigation.

PLAID is still investigating whether other data held in KARTE was affected.

What has not been disclosed:

  • Counts for integration credentials and imported data, or the number of affected customer companies.
  • An exact start time for the intrusion, beyond "the early hours of 13 November".
  • Whether any leaked credential was misused at a connected service.
  • Who was behind the attack, or when KARTE will come back.

Technical Information

Affected components. All 14 components on PLAID's status page, including event tracking, the admin console, API v2, KARTE Datahub, KARTE Message and KARTE for App, showed "Major Outage" as of PLAID's 17 November 15:52 JST (UTC+9) update.

Why integration keys matter. PLAID confirmed that integration credentials leaked and warned that, if they are not revoked, unauthorized access to the connected services could lead to unintended data writes or leakage. KARTE Datahub job flows move data into and out of KARTE, and KARTE's developer portal documents API v2, webhook and Amazon EventBridge integrations. Rescana guidance: depending on setup, the keys in scope can include API tokens, data warehouse or cloud storage credentials used by Datahub, and tokens for other SaaS tools. A credential revoked only on the KARTE side may still work at the service that issued it, so revoke it at the source.

What this is not. No CVE has been assigned, so there is no CVSS score or KEV listing.

Affected Product Versions

N/A — SaaS incident. There is no customer-installed KARTE version to upgrade.

  • In scope: every KARTE project. The service is stopped for all customers.
  • Confirmed data exposure: customer companies PLAID is contacting individually (data types listed above).
  • Most exposed (Rescana assessment): organizations that connected KARTE to other systems through API tokens, KARTE Datahub, webhooks or third-party integrations, or that imported customer records through linked tables.

Workaround and Mitigation

  1. Revoke every credential that connects KARTE to other services, as PLAID asked again in its 16 November notice. Rescana guidance: revoke each key or token at the system that issued it (data warehouse, cloud storage, CRM, email or messaging provider, ad platform), not only in KARTE. Issue replacements with least privilege, and do not load them into KARTE until PLAID says the service is safe to use.
  2. Check whether PLAID contacted you, both individually and at the fault and outage contact address you registered (Rescana guidance). Confirm that address is monitored.
  3. Review what customer data you imported into KARTE, including linked tables (Rescana guidance). Assess whether it contains personal information and whether your own notification duties apply.
  4. Warn staff with KARTE accounts about phishing. PLAID warned that suspicious emails impersonating it may reach registered KARTE account addresses. Do not open links or attachments in unexpected messages or enter login details.
  5. Review logs at the connected services (Rescana guidance). Look for use of KARTE-linked credentials from unfamiliar sources. PLAID dates the intrusion only to "the early hours of 13 November" JST (UTC+9), which was still 12 November in UTC, so start the review no later than 12 November 2026, 00:00 UTC (earlier if your logs allow) and continue it up to the time each credential was revoked. Shutting down KARTE does not disable keys that have already leaked.
  6. Plan for the outage (Rescana guidance) and follow PLAID's status page and 16 November notice.

Indicators of Compromise

PLAID has not published any indicators of compromise (IP addresses, request patterns or file hashes). Use your own logs at the services KARTE connected to, as described above.

What to Do With This Vendor Today (TPRM)

PLAID has confirmed that integration keys and some imported customer data leaked, so a supplier's KARTE setup can expose systems and records that concern you.

Ask suppliers that run websites, apps, e-commerce or customer communications for you or your customers:

  1. Do you use PLAID KARTE, directly or through an agency, on any site, app or campaign that touches our customers or data?
  2. Did PLAID contact you about this leak? If so, which of the published data types are involved, and did any imported data concern our customers?
  3. Have you revoked every secret key and access token that connects KARTE to other services, at the issuing service? Ask for the date and a list of the connected systems.
  4. Have you reviewed logs at those connected systems for unexpected use of KARTE-linked credentials?
  5. Will you send us PLAID's findings, and tell us before you restore KARTE? Check whether PLAID is on their subprocessor list.

If your own organization uses KARTE, ask your marketing and data teams the same questions and record the answers against the supplier record.

For a similar case of rotating SaaS integration secrets, see our advisory on the GitBook infrastructure breach.

Need help finding which suppliers use KARTE and tracking whether they have revoked their integration keys? Our team can help. Talk to an expert

Sources

Talk to an expert

Talk to Rescana about this advisory — or about how we help TPRM teams keep reviews moving.