1Password incident: 1Password Browser Extension Code Syntax Rendering Issue

1. postmortemJan 23, 2026, 20:05 UTC

   # Incident Postmortem - 1Password Browser Extension Code Syntax Rendering Issue **Customer impact began \(stable rollout start\):** 2025-12-09 **Investigation Started:** 2025-12-17 **Incident Declared \(UTC\):** 2025-12-30 13:13 **Fixed Release First Available:** 2026-01-01 **Fixed Release Fully Available and Verified:** 2026-01-05 **Incident Marked Resolved \(UTC\):** 2026-01-05 02:15 **Service\(s\) Affected:** 1Password browser extension ## Summary The 1Password browser extension, which works by injecting code into web pages, inadvertently included code from PrismJS, a third party dependency, breaking syntax highlighting on some websites that display code blocks. The issue was reported in beta in early December, escalated after additional customer reports and a report from an external partner, and required releasing a stable update to remove the problematic dependency chain. This issue affected page rendering only and did not expose vault data or credentials. ## Impact on C

2. resolvedJan 23, 2026, 20:04 UTC

   The 1Password browser extension, which works by injecting code into web pages, inadvertently included code from PrismJS, a third party dependency, breaking syntax highlighting on some websites that display code blocks.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in 1Password's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

How often does 1Password have incidents?

1Password reported 4 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 42 min. See 1Password's uptime and incident history