AI Tools

この記事はまだ翻訳されていません。英語版を表示しています。

チュートリアル7 分2026年11月14日執筆:AIGCDev更新日: 2026年11月18日

Notion AI security incident: review affected data and credentials

If you received a Notion email about the Fireworks AI security incident, you can open Notion yourself instead of following the email link. Switch to the relevant workspace and open the incident review from its sidebar. Confirm your role before reviewing the data available to you. If passwords or API keys were pasted into chats in an affected workspace during the incident's relevant period, treat them as potentially exposed and rotate them.

On November 18, 2026, we reviewed the incident status, download permissions, the effects of removing access, and what the CSVs contain. The steps follow Notion’s documentation. We did not test them in an affected workspace. Notion incident help page, security advisory.

Identify the workspace and your role

Notion says the Fireworks incident affects fewer than 1% of Notion workspaces and that affected customers have been contacted. The investigation is ongoing. If neither you nor your workspace owner has received a notice, Notion has not currently identified your workspace as affected and says no action is needed now. That does not guarantee it will never be identified as affected. The security advisory will be updated as the investigation continues.

  1. Open Notion yourself, sign in, and switch to the workspace named in the notice.
  2. In that workspace's sidebar, select ? → Security incident review. Labels may differ by language or version; check the official help page for the current instructions.
  3. Use the table below to identify what your role can access. If you belong to multiple workspaces, check the current workspace and your permissions in each. Opening a workspace alone does not mean you have opened the review, or that you can see all its affected data.
Your role Actions described by Notion
Workspace owner Use Download affected members to download the affected member list. Use Copy link to generate a link for affected members to review their own data.
Owner of a Business or Enterprise workspace with a verified domain Download the annotated CSV for the entire workspace (affected_content_annotated.csv).
Affected workspace member Download your own affected content from the same review page while access is available.

See the Notion help page for the role and access details. If an owner shares a link, confirm its source; if you prefer not to use it, try entering the review from the workspace yourself.

Organization owners can also download data by region for verified workspaces they can access under Org console → Data and Compliance → Security incident review. They can use a custom admin role to grant selected members permission to review and download data for the workspaces in scope without requiring them to be workspace owners. Notion help page on tools for owners.

Can't find the review or downloads?

Confirm that you selected the right workspace, then check your role and download permissions. If the workspace-wide annotated download is missing, check the plan and domain verification status. If the workspace owner has removed access, owners and members can no longer download the affected-content CSVs from the workspace. A missing button alone cannot tell you whether the workspace was affected.

If you still cannot establish access, ask the workspace owner to check the notice, member list, and permissions. Owners can contact Notion support through the help entry in Notion. Provide the workspace name, your role, your platform, and the missing entry or button; avoid sending passwords, complete keys, or CSV contents. If an email looks suspicious, you do not need its sign-in link: open Notion through a known entry point and check there.

Distinguish exposed content from added context

Save files using a secure method permitted by your organization and restrict access to those handling the incident. The files themselves may contain sensitive information. Do not upload a real CSV to a public analysis tool or paste its full contents into a ticket or group chat.

Notion provides affected_content.csv and affected_content_annotated.csv. The first contains affected content; the second adds analysis context to the same content. What you can see depends on your role. The official field descriptions distinguish:

Field or file How to interpret it
message_role Identifies whether the message came from a user or the AI model.
text The affected message text, including user inputs and AI assistant outputs. Check it for credentials, customer information, and other sensitive material.
__metadata Context Notion added after the incident to help with analysis, including record, user, and thread IDs. __metadata_source_date shows when the data was sent to Fireworks, typically within a day of the interaction. These columns were not exposed in the incident.
__analysis Flags potentially sensitive information in affected conversations to help review. Treat it as a lead: no flag does not prove the content is safe. Review the content as well.
CSV from Download affected members Lists names, email addresses, membership status, user IDs, and counts of affected data rows associated with each user. Owners can use it to coordinate review; the row count is not a severity score.

Notion says the affected dataset included Notion AI chat transcripts used for Insights. The vast majority of affected transcripts lacked automatically added user and workspace identifiers, but the chat text itself could contain identifying or sensitive information. The affected data included the full text of user messages and assistant replies. It could include text a user selected on a page or excerpts from pages, databases, or tool results cited in the reply. Tool activity itself was outside the scope for the vast majority of affected transcripts. AI Meeting Notes content could be affected if it appeared in a user message or the assistant referenced it in a reply. Notion security advisory, help page.

Respond to potentially exposed credentials

Notion recommends treating affected data as exposed and immediately rotating passwords, API keys, and other credentials pasted into Notion AI during the relevant period. If an identified affected workspace cannot download the data yet, its team can still start with credentials known to have been pasted into chats during that period. Follow your organization's incident process and contact the credential owner or security team. Share the service, purpose, owner, and status without sending the credential value.

  1. Identify the service and owner from the affected text and your own records. Prioritize credentials that are still valid, have elevated permissions, or affect production.
  2. Rotate credentials and update dependent applications through the service's official management interface or the responsible owner; use the service's reset process for passwords. Follow the service and organization's incident procedures for order and verification. Do not delay emergency revocation of a credential known to be abused while creating a replacement.
  3. Confirm the old credential is invalid and the replacement works, and review relevant usage records under your organization's process. Record the owner, completion time, and follow-up items without recording secret values.

Notion says it revoked the Notion API keys it found in affected messages on November 11. Its November 13 update says it reported the third-party API keys it found to their issuers on November 12. Check the status of third-party credentials with the issuing services and respond to any credentials you find. Notion security advisory.

Workspace owners should download and review the files they need under their organization’s procedures before selecting Remove access to affected content on the review page. This removes access to affected-content CSVs for the entire workspace, so owners and members can no longer download them from the workspace. The underlying data, Notion AI chat history, and retention settings are unaffected. Handle any exposed credentials separately. Notion help page.

For day-to-day meeting notes and search after the incident review, see the Notion AI workflow guide.

notion-aisecuritydata-privacy