Treasure AI is assessing recently disclosed PHP and Node.js vulnerabilities, the eMudhra certificate security incident, and the PingCAP/TiDB security incident.
This page summarizes potential impact to the Treasure AI service, the actions we are taking, and any steps customers may need to take.
Latest update - November 5, 2026, 5:30 PM EST: Treasure AI has completed the required patching and other remediation for all identified high-risk systems associated with the issues covered in this post, including affected public-facing services. We have also implemented compensating controls to provide additional protection alongside these updates.
|
Item |
Treasure AI assessment |
|
PHP vulnerabilities |
Our investigation is complete and has not identified PHP in the production environment supporting the Treasure AI service. Previously identified legacy PHP sites outside the service have been shut down. Based on our findings, no known customer impact or additional remediation for the Treasure AI service is currently indicated. |
|
Node.js vulnerabilities |
Required runtime updates have been completed for affected public-facing services and the remaining identified AWS Lambda workloads. Additional protections against the Brotli-related vulnerability have also been implemented. |
|
eMudhra certificate incident |
Required certificate-trust updates have been completed for identified high-risk systems, with additional controls implemented to strengthen certificate validation. Updated Workflow Custom Script images remain available; customers using older images should follow the guidance below. |
|
Apache Tomcat security advisories |
The Tomcat deployment reviewed is restricted to internal network access. Security assessments and updates follow our established risk-based vulnerability and patch management processes. |
|
PingCAP/TiDB incident |
Our investigation is complete and has not identified current or historical use of PingCAP/TiDB Cloud in the production environment supporting the Treasure AI service. Based on our findings, no known customer impact or remediation for the Treasure AI service is currently indicated. |
Our IR teams have completed their investigation into potential exposure to CVE-2026-109618 and CVE-2026-109619. The review did not identify PHP in the production environment supporting the Treasure AI service, and we did not identify a need for additional remediation in that environment. As previously reported, the identified legacy sites using PHP outside the Treasure AI service have been shut down. We consider this investigation complete and will reassess our findings if new information becomes available. Additional details regarding this vulnerability are available in the official PHP advisory.
We have completed the required Node.js runtime updates for affected public-facing services, including the remaining AWS Lambda workloads identified during our review. We have also implemented protections that block inbound requests using Brotli encoding before they reach protected services, providing additional protection alongside the runtime updates. We will continue to assess and maintain our environment through our established risk-based vulnerability and patch management program. Additional details regarding this vulnerability are available in the official Node.js advisory.
We have completed the required certificate-trust updates for identified high-risk systems, including affected public-facing services. We have also implemented additional controls to strengthen certificate validation and reduce risks associated with the affected eMudhra certificate chains. Validation performed to date has confirmed rejection of the affected certificate chains used in testing. Customers using older Workflow Custom Script images should follow the customer guidance below. We will continue to assess and maintain our environment through our established risk-based vulnerability and patch management program. Additional details regarding this vulnerability are available in the official eMudhra statement.
Our review identified Tomcat usage in the production environment supporting the Treasure AI service. The deployment reviewed is restricted to internal network access and is not directly accessible from the public internet. This assessment concerns Tomcat software vulnerabilities. Java certificate-trust updates associated with the eMudhra incident are covered in the eMudhra assessment above. We will continue to assess and maintain our environment through our established risk-based vulnerability and patch management program. Additional details regarding this vulnerability are available in the official Apache announcement.
Our IR teams have completed their investigation into potential exposure to the PingCAP/TiDB security incident. The review has not identified current or historical use of PingCAP/TiDB Cloud by Treasure AI, and we have not identified customer impact or a need for remediation within the Treasure AI service. We consider this investigation complete and will reassess our findings if new information becomes available. Additional details regarding the incident are available in the official PingCAP notice.
With the identified high-risk exposure that could affect customers addressed through patching and additional protective controls, we do not plan further updates to this post. Work to identify and address lower-risk internal systems will continue through our normal risk-based vulnerability and patch management processes. For questions specific to your organization, please contact Treasure AI Support through your usual support channel or reach out to the Treasure AI Security team at security@treasure.ai directly.