LexisNexis pulls three services offline after suspicious server activity
- ID
- 12759
- Status
- summarized
- Published
- 11 Aug 2026, 12:15 AM
- Fetched
- 11 Aug 2026, 12:34 AM
- Provider
- The Register
- Category
- technology
- Original URL
- https://www.theregister.com/off-prem/2026/08/10/lexisnexis-blames-outage-on-unusual-server-activity/5285541
- Source URL
- https://www.theregister.com/headlines.atom
Summary
- Score
- 4.0
- Created
- 11 Aug 2026, 12:36 AM
- Tags
- Audience
- developersdatabase_learners
What happened
LexisNexis took Diligence, Metabase API, and Newsdesk offline after detecting unusual activity on third-party vendor-managed servers. Diligence returned over the weekend with partial content; Newsdesk and Metabase API were expected back progressively on Monday. LexisNexis explicitly stated the outage is NOT connected to the CVSS 10.0 SQL injection flaw disclosed by Metabase (the BI platform) on August 6, which has already been linked to a confirmed breach at laptop maker Framework.
Why it matters
If you run Metabase BI in your stack, the CVSS 10.0 SQL injection zero-day disclosed August 6 is the actionable item here, not the LexisNexis outage. Patch or check your Metabase instance immediately. The LexisNexis story itself is a reminder that third-party vendor dependencies can take your service offline for days with no clear timeline.
Discussion angle
The Metabase BI zero-day (CVSS 10.0, no CVE yet) is the real signal buried in this article — who in the community runs Metabase, and has anyone verified their exposure?