Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability
Chargebee reports no impact from the PHPshell zero-day vulnerability on its Product Security component. Chargebee states that it does not use PHP in customer-facing workflows. The provider continues to monitor the situation and no customer action is required.
State
Monitoring
Started
10 d ago
2026-10-22 15:43 UTC
Ongoing for
10 days
Worst impact
Notice
Timeline
1 updateMonitoring
10 days 100%
Updates
Times in UTCAs posted by Chargebee
Chargebee is aware of the recently reported PHPshell zero-day vulnerability and has completed an initial assessment of its potential impact on our services. Chargebee does not use PHP in its customer-facing workflows. Based on our assessment, this vulnerability does not affect Chargebee’s services or customer integrations, and no action is required by our customers at this time. As an additional precaution, we are verifying with our subprocessors to confirm they are unaffected and to ensure appropriate safeguards remain in place across our service ecosystem. We will continue to monitor relevant security developments and provide updates if our assessment changes. If you have any questions, please contact Chargebee Support.
Affected components
1Chargebee in the last 90 days
Full historyIncidents in 90 days
14
Days with an incident
21
Median duration
22 min
This incident
674× the median
Other Chargebee incidents
All incidentsChargebee·API Service Degradation - EU Region
This incident has been resolved.
Chargebee·API Service Degradation
We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have completely recovered. We apologize for any disruption this may have caused.
Chargebee·API Service Degradation - EU Region
This incident has been resolved.
Chargebee·API Service Degradation
We experienced a brief service interruption in the EU region between 09:14 UTC and 09:20 UTC that resulted in failed API requests for some merchants. Services have recovered. We apologize for any disruption this may have caused.
Chargebee·API Service Degradation
This incident has been resolved.
Follow Chargebee
Your coding agent knows when Chargebee is down, and tells you when a failure is theirs, not yours. You can also get Chargebee 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.cc/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 "chargebee" and tell me if Chargebee 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.cc/feed.xml?providers=chargebee/feed subscribe https://outages.cc/feed.xml?providers=chargebeeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane