Live  /  Chargebee  /  Incident

Chargebee: Subject: Security Notice: No Impact from PHPshell Zero-Day Vulnerability

Chargebee · chargebee.comResolved2026-11-03 07:07 UTC
Public — what happened

Summary

Chargebee posted a security notice on 2026-10-22 about a recently reported zero-day vulnerability called PHPshell. The company said it had finished an initial review and concluded that its services and customer integrations are not affected, because it does not use PHP in its customer-facing workflows. Chargebee said customers do not need to do anything, and that it was checking with its subprocessors to confirm they are also unaffected. The notice was marked resolved on 2026-11-03, and the company said it would share an update only if its assessment changed.

Affected

Product Security

As listed on Chargebee’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Chargebee against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Chargebee: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Chargebee report →

More from Chargebee

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Chargebee status & history page.

Related: Chargebee status & history. SquidGrid is not affiliated with Chargebee.