Live

Security Notice: No Impact to Chargebee Services from Recent NGINX & Java4shell CVEs

Major outageOfficial update
0

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 updates
17:2917:3417:4017:4517:50
Major outageUpdate postedTimes in UTC

Investigating

21 min 100%

Updates

Times in UTC

As posted by Chargebee

Investigating

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.

Investigating

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

1
Product Security

Chargebee in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

19

Days with an incident

28

Median duration

57 min

This incident

63% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 days
median 57 min
90 days agoToday

Other Chargebee incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=chargebee
Slack
/feed subscribe https://outages.live/feed.xml?providers=chargebee

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane