Java4Shell vulnerability assessment and mitigation
Notion is investigating the Java4Shell vulnerability. Notion reports no evidence of customer impact or public exploitation affecting Notion at this time. The status is investigating.
State
Investigating
Started
Ongoing for
15 min
Worst impact
Notice
Timeline
1 updateInvestigating
15 min 100%
Updates
Times in UTCAs posted by Notion
We’re investigating the newly disclosed Java4Shell vulnerability and assessing any potential exposure within Notion. At this time, we have no evidence of customer impact or public exploitation affecting Notion, and we’re applying mitigations and working with relevant vendors as needed. This is unrelated to the Fireworks incident.
Notion in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
34
Median duration
3 h 39 min
This incident
93% shorter than the median
Other Notion incidents
All incidentsNotion·Login with Apple unavailable
Login with Apple did not work in Notion because of an outage in Apple's sign-in service. Notion reports that the incident is resolved. The outage lasted 5 hours and 41 minutes.
Notion·Issues with outlook connections
Notion Outlook connections had degraded service. This affected Outlook integrations such as mail and calendar. Notion reports that the issue is resolved. The outage lasted about 25 hours.
Notion·Some Notion Agent sessions may hang or stop updating
Some Notion Agent sessions hung or stopped updating, so new responses did not appear in the chat. Notion identified the issue and stated that refreshing the page restored the session. Notion reported that the incident is resolved. It lasted about 2 hours and 20 minutes.
Notion·Users unable to access Notion
The issue affecting access to Notion has been resolved. Signing in, loading pages, and viewing and editing content are working normally again. Thank you for your patience.
Notion·PHP2Shell (CVE-2026-109618, CVE-2026-109619)
Please visit our Security Advisories page at for any future updates.
Follow Notion
Your coding agent knows when Notion is down, and tells you when a failure is theirs, not yours. You can also get Notion incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "notion" and tell me if Notion has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=notion/feed subscribe https://outages.live/feed.xml?providers=notionFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane