Security Notice: No Impact to Chargebee Services from Recent NGINX & Java4shell CVEs
Chargebee reports a security assessment for the Product Security component after recent NGINX and Java4shell CVEs. Chargebee states that the listed vulnerabilities do not affect its services or customer integrations, and no customer action is required. Chargebee reports the status as investigating and has applied recommended security patches.
State
Investigating
Started
Ongoing for
21 min
Worst impact
Major outage
Timeline
2 updatesInvestigating
21 min 100%
Updates
Times in UTCAs posted by Chargebee
Chargebee is aware of the recently reported CVEs related to NGINX (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425 (all CVSS 9.2)) and Java4shell and has completed an assessment of their potential impact on our services. Based on our assessment, the vulnerabilities listed above do not affect Chargebee’s services or customer integrations, and no action is required by our customers at this time. As an additional precaution, recommended security patches have been applied at both the perimeter and host levels to ensure that appropriate safeguards remain in place across our service ecosystem. We will continue to monitor and provide updates if our assessment changes. If you have any questions, please contact Chargebee Support.
Chargebee is aware of the recently reported CVEs related to NGINX (CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810, CVE-2026-113425 (all CVSS 9.2)) and Java4shell and has completed an assessment of their potential impact on our services. Based on our assessment, the vulnerabilities listed below do not affect Chargebee’s services or customer integrations, and no action is required by our customers at this time. As an additional precaution, recommended security patches have been applied at both the perimeter and host levels to ensure that appropriate safeguards remain in place across our service ecosystem. We will continue to monitor 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
19
Days with an incident
28
Median duration
57 min
This incident
63% shorter than the median
Other Chargebee incidents
All incidents
Chargebee·API Service Degradation
Chargebee reported degraded API service and API endpoint performance in the US region. Chargebee later stated that a brief cloud provider issue caused intermittent API failures for some US merchants, and that services recovered. Chargebee resolved the incident after about 147 minutes.

Chargebee·API Service Degradation
Chargebee reported degraded API service in the US region. The API (US) and API Endpoints - API (US) components had intermittent failures. Chargebee reports that the incident is resolved and that it lasted 83 minutes.

Chargebee·Microsoft 365 Service Degradation
Chargebee reports degraded email notifications for Microsoft 365 and Email & SMTP Services - Microsoft 365. Chargebee later confirmed that Microsoft restored the Microsoft 365 services and that custom SMTP email notifications work again. The incident is resolved and lasted about 29 hours.

Chargebee·Partially Degraded Service
Chargebee reports that the Slack Apps/Integrations/APIs component did not work correctly. Chargebee reports that this problem is resolved. The problem lasted 3 minutes.

Chargebee·Partially Degraded Service
Chargebee reported partially degraded service on Slack Apps/Integrations/APIs. Chargebee reports that the incident is resolved. The incident lasted 213 minutes.
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.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 "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.live/feed.xml?providers=chargebee/feed subscribe https://outages.live/feed.xml?providers=chargebeeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane