Obsidian Security Status
Real-time updates of Obsidian Security issues and outages
Obsidian Security status is Operational
Connections (SaaS Applications)
Obsidian Security Security Advisory
Lior Grossman
Maker of StatusSight
I built StatusSight. Here's what I'm building next with AI.
In Lior Builds, my free newsletter, I share one story from a product I built with AI, plus short notes on the tools and models worth using: what worked, what did not, and the numbers behind it. Every week or two.
Active Incidents
Security Advisory: Node2Shell Vulnerability (CVE-2026-111497) Published: Oct 27, 2026
Summary Obsidian Security has assessed the recently disclosed vulnerability known as Node2Shell (CVE-2026-111497), also referred to as HTTP2Shell.
Our response We identified a limited number of affected services and are actively patching and redeploying them.
As an immediate mitigation, we implemented Brotli content-encoding blocking at our production API gateways (completed Oct 26, 2026), protecting against Node2Shell and related HTTP2Shell variants.
Customer Impact We have observed no customer impact to date. We will update this advisory once the patching is completed on our side.
Questions For questions, please contact your Obsidian account team or support via [email protected] or the Admin Portal.
Security Advisory: eMudhra Intermediate CA Compromise Published: Oct 20, 2026 | Last updated: Oct 21, 2026
Summary On October 20, 2026, a security issue affecting several intermediate certificate authorities (CAs) operated by eMudhra was publicly disclosed (https://emudhra.we-have-a-problem.com/). The flaw could allow a third party to issue fraudulent TLS certificates for arbitrary domains. This is an industry-wide issue affecting any system that trusts the affected CAs. It is not the result of a compromise of Obsidian Security systems.
Our response Obsidian Security began investigating promptly following disclosure. Exploiting this issue requires an attacker to intercept network traffic in addition to holding a fraudulent certificate. Based on our investigation to date, we have found no evidence that this issue was exploited against Obsidian Security systems or customer data.
- We are taking all precautionary measures to prevent this issue from being exploited in our environments:
- We retired all at-risk certificates from all corporate endpoints
- We have gated our software build pipelines so that only systems with updated trust stores can build and release code
- We have updated all Obsidian connectors to remove trust for the affected CAs.
- We are removing trust in the affected certificate authorities across our production platform, data collection services, and build infrastructure
- Tracking the response of our critical third-party providers
Customer Impact
UPDATE Oct 21, 2026 - All Connectors have been updated and data retrieval has resumed.
Obsidian Connectors to third party enterprise applications will be paused for up to four (4) hours from 23:45 GMT on Oct 20th, 2026. We will re-enable each connector as it is addressed. Data streaming from paused connectors should resume without data loss. This post will be updated when all data connectors have been addressed and restarted.
Questions Please contact Obsidian Support at [email protected] or via the Obsidian Admin portal. We will update this advisory if our assessment changes.
Recently Resolved Incidents
Security Advisory: GitBook Security Incident Published: Nov 3, 2026
Summary Obsidian Security has assessed the security incident disclosed by GitBook on November 3, 2026, in which an attacker gained unauthorized access to some of GitBook’s infrastructure credentials. Obsidian uses GitBook to host the Obsidian Help Center documentation. GitBook has reported no evidence that documentation content was modified.
Our response As response, we have rotated all GitBook access tokens and related credentials across our environments and confirmed documentation access is working as expected. The Obsidian platform, its supporting infrastructure, and customer data are not hosted on GitBook.
Customer Impact We have observed no customer impact to date. No customer action is required. Customers accessing the Obsidian Help Center through the Documentation link in the Obsidian UI should re-authenticate automatically. We will update this advisory if our assessment changes.
Questions For questions or any issues with accessing our product documentation, please contact your Obsidian account team or support via [email protected] or the Admin Portal.
Obsidian Security Outage Survival Guide
You're checking on Obsidian Security - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Obsidian Security Components
Obsidian Security Platform Services
Admin Portal and UI
Admin Authentication & SSO
Connections (SaaS Applications)
Security Advisory: eMudhra Intermediate CA Compromise Published: Oct 20, 2026 | Last updated: Oct 21, 2026
Summary On October 20, 2026, a security issue affecting several intermediate certificate authorities (CAs) operated by eMudhra was publicly disclosed (https://emudhra.we-have-a-problem.com/). The flaw could allow a third party to issue fraudulent TLS certificates for arbitrary domains. This is an industry-wide issue affecting any system that trusts the affected CAs. It is not the result of a compromise of Obsidian Security systems.
Our response Obsidian Security began investigating promptly following disclosure. Exploiting this issue requires an attacker to intercept network traffic in addition to holding a fraudulent certificate. Based on our investigation to date, we have found no evidence that this issue was exploited against Obsidian Security systems or customer data.
- We are taking all precautionary measures to prevent this issue from being exploited in our environments:
- We retired all at-risk certificates from all corporate endpoints
- We have gated our software build pipelines so that only systems with updated trust stores can build and release code
- We have updated all Obsidian connectors to remove trust for the affected CAs.
- We are removing trust in the affected certificate authorities across our production platform, data collection services, and build infrastructure
- Tracking the response of our critical third-party providers
Customer Impact
UPDATE Oct 21, 2026 - All Connectors have been updated and data retrieval has resumed.
Obsidian Connectors to third party enterprise applications will be paused for up to four (4) hours from 23:45 GMT on Oct 20th, 2026. We will re-enable each connector as it is addressed. Data streaming from paused connectors should resume without data loss. This post will be updated when all data connectors have been addressed and restarted.
Questions Please contact Obsidian Support at [email protected] or via the Obsidian Admin portal. We will update this advisory if our assessment changes.
Action Policies
Reporting
Workflow Integrations
API
Obsidian Security Posture Management
Obsidian Security Threat Management
Obsidian Security Integration Management
Obsidian Security Extend
Obsidian Security Security Advisory
Security Advisory: eMudhra Intermediate CA Compromise Published: Oct 20, 2026 | Last updated: Oct 21, 2026
Summary On October 20, 2026, a security issue affecting several intermediate certificate authorities (CAs) operated by eMudhra was publicly disclosed (https://emudhra.we-have-a-problem.com/). The flaw could allow a third party to issue fraudulent TLS certificates for arbitrary domains. This is an industry-wide issue affecting any system that trusts the affected CAs. It is not the result of a compromise of Obsidian Security systems.
Our response Obsidian Security began investigating promptly following disclosure. Exploiting this issue requires an attacker to intercept network traffic in addition to holding a fraudulent certificate. Based on our investigation to date, we have found no evidence that this issue was exploited against Obsidian Security systems or customer data.
- We are taking all precautionary measures to prevent this issue from being exploited in our environments:
- We retired all at-risk certificates from all corporate endpoints
- We have gated our software build pipelines so that only systems with updated trust stores can build and release code
- We have updated all Obsidian connectors to remove trust for the affected CAs.
- We are removing trust in the affected certificate authorities across our production platform, data collection services, and build infrastructure
- Tracking the response of our critical third-party providers
Customer Impact
UPDATE Oct 21, 2026 - All Connectors have been updated and data retrieval has resumed.
Obsidian Connectors to third party enterprise applications will be paused for up to four (4) hours from 23:45 GMT on Oct 20th, 2026. We will re-enable each connector as it is addressed. Data streaming from paused connectors should resume without data loss. This post will be updated when all data connectors have been addressed and restarted.
Questions Please contact Obsidian Support at [email protected] or via the Obsidian Admin portal. We will update this advisory if our assessment changes.
Security Advisory: Node2Shell Vulnerability (CVE-2026-111497) Published: Oct 27, 2026
Summary Obsidian Security has assessed the recently disclosed vulnerability known as Node2Shell (CVE-2026-111497), also referred to as HTTP2Shell.
Our response We identified a limited number of affected services and are actively patching and redeploying them.
As an immediate mitigation, we implemented Brotli content-encoding blocking at our production API gateways (completed Oct 26, 2026), protecting against Node2Shell and related HTTP2Shell variants.
Customer Impact We have observed no customer impact to date. We will update this advisory once the patching is completed on our side.
Questions For questions, please contact your Obsidian account team or support via [email protected] or the Admin Portal.
Security Advisory: GitBook Security Incident Published: Nov 3, 2026
Summary Obsidian Security has assessed the security incident disclosed by GitBook on November 3, 2026, in which an attacker gained unauthorized access to some of GitBook’s infrastructure credentials. Obsidian uses GitBook to host the Obsidian Help Center documentation. GitBook has reported no evidence that documentation content was modified.
Our response As response, we have rotated all GitBook access tokens and related credentials across our environments and confirmed documentation access is working as expected. The Obsidian platform, its supporting infrastructure, and customer data are not hosted on GitBook.
Customer Impact We have observed no customer impact to date. No customer action is required. Customers accessing the Obsidian Help Center through the Documentation link in the Obsidian UI should re-authenticate automatically. We will update this advisory if our assessment changes.
Questions For questions or any issues with accessing our product documentation, please contact your Obsidian account team or support via [email protected] or the Admin Portal.