Notion revokes exposed keys; llm fixes misrouted credentials
Notion says it revoked exposed Notion API keys on November 11, while a separate llm 0.37.2 update fixes configurations that could send an OpenAI key to another endpoint.
Notion says it revoked exposed Notion API keys on November 11 following the Fireworks incident.
That action covers its own keys, not passwords or another provider’s credentials pasted into affected messages. Affected users should review the identified material and replace other exposed credentials at the issuing service. [1][2]
Separately, llm 0.37.2 fixes two credential-routing paths. A custom endpoint with a missing named key could fall back to the OpenAI environment key. A second path lost credential settings when switching a custom Responses endpoint to Chat Completions. Both could send the wrong key to the configured endpoint. The advisories identify vulnerable configurations, not an observed attack on every installation. [3][4][5]
Upgrade llm with the command for your installation method and review custom endpoints. If a vulnerable configuration may have transmitted a key, replacing that key is a separate step from installing the patch. [6]
Notion’s affected-content review requires a current desktop browser; checking only on mobile is insufficient. Notion says workspaces without an affected-workspace notice currently need no action. [1][2]
Take it further
Upgrade llm For users of llm; follow the command matching your installation method. No deadline stated.
Review the Notion incident Affected workspaces and members; use the current desktop browser. Content download requires a verified domain. No deadline stated.
Sources & details 8 sources
Discuss in your voice app
Take the reporting, visual explanations and original sources into a conversation. Copy the brief, paste it into your preferred assistant, then start its voice mode.
Paste the brief into your voice app to discuss this reporting.Revised 12 November 2026. Revised visual explanations and copy; added Nvidia investigation context and clarified tool eligibility.
Reporting sources
- Notion · November 11 incident update
Dated revocation update, notification scope and advice to rotate other exposed credentials. Revocation is Notion’s account, not an independently observed operation.
- Notion · incident-review instructions
Desktop-browser access; owner and member review roles; verified-domain requirement for affected-content downloads. No private workspace was opened.
- llm · version 0.37.2
November 11 release containing both credential-routing fixes.
- llm · missing-key fallback advisory
GHSA-v9h7-jj4g-f862. Affected versions 0.6 through versions before 0.37.2; configuration-dependent exposure.
- llm · Responses delegation advisory
GHSA-r639-rr7r-x72w. Affected versions 0.32a2 through versions before 0.37.2; custom endpoint plus Chat Completions opt-out path.
- llm · upgrade instructions
Use the upgrade command matching pip, pipx, uv or Homebrew. This report did not execute an upgrade.
- llm · patched implementation
Tagged 0.37.2 source independently inspected: custom endpoints clear key_env_var; synchronous and asynchronous delegates preserve needs_key and key_env_var.
- Fireworks · underlying incident bulletin
Separate first-party confirmation of the underlying incident. Does not verify Notion’s key-revocation operation.
Images & figures
Patching a credential-routing flaw and invalidating an exposed credential address distinct failures in separate products.
Euangelion · Source · Usage terms · Download figure