Sprinklr Response to Oracle Critical Security Patch Update - Nov 2026
Sprinklr Logo

Security Trust Portal

Start your security review
View & download sensitive information
Ask for information
ControlK

The Sprinklr platform is built with cyber security and data privacy in its design. This Trust Center provides details on Sprinklr’s extensive security and privacy program including policies, procedures, and standards.

  • Ford Motor Company
  • Heineken
  • LG Electronics
  • Honda Motor Co
  • Acer
  • PRADA
  • Hyundai
  • SimpliSafe
  • Superdry
  • UBS
  • PUMA
  • Crocs
  • Princess Cruises
  • Canon
  • Amtrak
  • LATAM Airlines
  • Aramex
  • Greggs

Documents

Featured Documents

DOCUMENTSSprinklr Security Program Overview

Security Trust Portal Updates

Sprinklr Response to Oracle Critical Security Patch Update - Nov 2026

Vulnerabilities

Status: Interim mitigation in progress

To protect the stability of our services, our teams performed additional quality assurance and stability testing before rolling out the Base64 acceleration mitigation. As a result, the timeline has changed from our earlier estimate. The rollout has now commenced, and, barring any technical or stability issues observed in our platform, we expect the mitigating controls to be fully enabled globally within 24 hours.

No action is required from customers at this time. We will continue to post updates on the Sprinklr Trust Portal, and your account team can escalate any questions to our Security team.

Status: Remediation in progress

Overview
Thank you for your patience. Our Security and Engineering teams have completed an initial analysis. A small subset of our internet-accessible endpoints, reached via our load balancer, is affected by this vulnerability.

Remediation
As an interim measure, we have begun disabling Base64 acceleration to mitigate known exploitable paths while we await a patch from our vendor.

Customer Action
No action is required from customers at this time. We will continue to post updates here on the Sprinklr Trust Portal, and your account team can escalate any questions to our Security team.

Status: Assessment complete; remediation in progress

Overview
Oracle has published security advisories affecting multiple Oracle products. Sprinklr’s Security and Engineering teams have conducted an extensive investigation of our systems and services for impact and are pursuing mitigations as/if needed.

Impact on Sprinklr
Sprinklr is leveraging OpenJDK v.17.x and x.21.x within our environments. We are validating the exploitability of all components, with priority given to internet-accessible services.

Remediation
We are awaiting a patch from our vendor and will plan to apply it across all production environments accordingly and as soon as possible, in accordance with our vulnerability management program. Updates will be provided on this Sprinklr Trust Portal.

Customer actions
No action is required from customers at this time.

Questions
Please contact your Sprinklr account team, who will escalate to Security internally.

Last updated: November 17 2026, 2:00pm ET | Status: Assessment in progress
Thank you for reaching out. Our Security and Engineering teams are reviewing Oracle's recently announced security update and assessing any potential impact to Sprinklr systems and services. We will share an update with more information as soon as possible.

Sprinklr Response to Node2Shell CVE-2026-111497 Vulnerabilities

Vulnerabilities

Last updated: November 6, 2026, 8am ET | Status:  Remediation in progress   
  
Remediation Update:  
The first environment was fully patched on November 5th, as planned. Based on observations and key performance metrics, the remaining environments commencing on or after Nov. 16th. 

Customer actions  
No action is required from customers at this time. 

Ongoing monitoring    
Our Security team continues to monitor Sprinklr systems and will respond to any issues that arise. We will keep investigating and addressing potential vulnerability reports as quickly as possible.  

Questions  
Please contact your Sprinklr account team who will escalate to Security internally.

Last updated: October 29, 2026, 11am ET | Status:  Assessment complete; remediation in progress  

Impact on Sprinklr  
Sprinklr Security and Engineering teams have completed a detailed assessment of our systems. While we have confirmed Node.js components within the Sprinklr environment, we have determined that this vulnerability cannot be successfully exploited within the Sprinklr environment.    

Remediation  
The Node.js components will be patched across all production environments in accordance with our vulnerability management program. Internet-facing components will be prioritized, beginning November 5th with remaining environment commencing on Nov. 16th.   

Customer actions  
No action is required from customers at this time. 

Ongoing monitoring    
Our Security team continues to monitor Sprinklr systems and will respond to any issues that arise. We will keep investigating and addressing potential vulnerability reports as quickly as possible.  

Questions  
Please contact your Sprinklr account team who will escalate to Security internally.

Last updated: October 23, 2026, 1pm ET | Status: Assessment in progress 

Overview  
Node.js has published security advisories for a vulnerability named Node2Shell (CVE-2026-111497). Sprinklr’s Security and Engineering teams have conducted an extensive investigation of our systems and services for impact and are pursuing mitigations as/if needed. 

Impact on Sprinklr  
Our assessment confirmed Node.js components within the Sprinklr environment. We are validating the exploitability of those components, with priority given to internet-accessible services. 

At this time, we have found no evidence that this vulnerability can be or has been successfully exploited within the Sprinklr environment. 

Remediation  
The Node.js components will be patched across all production environments in accordance with our vulnerability management program. Updates will be provided on this Sprinklr Trust Portal. 

Customer actions  
No action is required from customers at this time. 

Questions  
Please contact your Sprinklr account team who will escalate to Security internally.

Sprinklr Response to PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619

Vulnerabilities

Last updated: October 22, 2026, 8:00 AM ET | Status: Remediation Complete 

The affected PHP functionality present on a limited number of internal endpoints have been successfully updated to the latest PHP version. Our Security team continues to monitor Sprinklr systems and will respond to any issues that arise. 

Last updated: October 21, 2026, 5:00 PM ET | Status: Assessment complete; remediation in progress 

Overview  
The PHP Group has published security advisories for CVE-2026-109618 and CVE-2026-109619 (PHP Security Advisory). Sprinklr’s Security and Engineering teams reviewed the advisories and completed an assessment of our systems and services. 

Impact on Sprinklr  
The affected PHP functionality is present on a limited number of internal endpoints that are not exposed to the internet. As of 5:00 PM ET on October 21, 2026, we have found no evidence of exploitability or exploitation. 

Remediation  
We will patch the affected components across all production environments in accordance with our vulnerability management program. 

Ongoing monitoring  
Our Security team continues to monitor Sprinklr systems and will respond to any issues that arise. We will keep investigating and addressing potential vulnerability reports as quickly as possible. We will update this article as new information becomes available. 

Customer actions  
No action is required from customers at this time. 

Questions  
Please contact your Sprinklr account team who will escalate to Security internally.  

Reporting a suspected security incident to Sprinklr

Incidents

If you are a Sprinklr customer and suspect a security issue or have a related concern, please notify your Sprinklr Account team or submit a support ticket by emailing tickets@sprinklr.com.

All reported security concerns are promptly escalated to Sprinklr’s Security Incident Response Team (SIRT) for review and investigation. From that point forward, the matter is managed in accordance with Sprinklr’s established Incident Response processes.

Sprinklr’s Vulnerability Disclosure Program

Vulnerabilities

If you believe you have found a vulnerability in our products, please responsibly disclose this information to us through our HackOne bug bounty program. You will be recognized for your efforts if you were the first to report a valid vulnerability as per the rules of the vulnerability disclosure program.

More details about Sprinklr’s Vulnerability Disclosure Program and how to submit can be found here: https://www.sprinklr.com/responsible-disclosure/

Built onSafeBase by Drata Logo