Security¶
Warning
Please read the important note below on October/November 2026 vulnerabilities
- Authentication
- Project Access
- Project folders - defaults and access
- Permissions
- Connections security
- User profiles
- Shared objects
- Authorized objects
- Secrets Manager
- User secrets
- Audit Trail
- Govern Security: Permissions
- Passwords security
- Advanced security options
- Stories security
- Messaging Channels Permissions
How Dataiku responds to the October/November 2026 vulnerabilities¶
Dataiku takes steps to ensure the security of its customers among the large number of severe ecosystem vulnerabilities reported since the second half of October 2026
Applicable to all customers¶
nginx2root¶
Dataiku uses nginx but is not affected by any of the 5 vulnerabilities in the “nginx2root” disclosure.
Dataiku does not enable HTTP/2 on any of its nginx servers. Dataiku is not affected by the two main vulnerabilities (CVE-2026-123007 and CVE-2026-123633).
Dataiku does not enable HTTP/3 (aka QUIC) either and is not affected by CVE-2026-121810.
Dataiku does not use mail proxying and is not affected by CVE-2026-113425.
Dataiku does not use the “mirror” feature and is not affected by CVE-2026-123634.
PHP2Shell¶
Dataiku does not use PHP and is not affected by the “PHP2Shell” classes of vulnerabilities
Applicable to Dataiku Cloud Customers¶
Note: this does not apply to “Cloud Dedicated” customers. See below for “Cloud Dedicated”
Java Base64 memory corruption / CVE-2026-114938¶
Dataiku Cloud is not affected. No further action is required.
Linux TCP use-after-free / CVE-2026-98432¶
All Dataiku Cloud customers have already been updated to a non-vulnerable version.
Node.js / Brotli decoder¶
Dataiku’s use of Node.js is limited. Dataiku has specifically reviewed the vulnerabilities reported in Node.js, notably the Brotli decoder vulnerability and our assessment confirms that Dataiku is not affected by these vulnerabilities.
Nevertheless:
Customers on version 14.7.7 have been updated to a non-vulnerable version
Customers on version 15.2.2 have been updated to a non-vulnerable version
Customers on version 15.0.3 are strongly encouraged to update to version 15.2.2, which is available as a self-service update from the Launchpad.
Oracle Java¶
Dataiku Cloud does not use Oracle Java.
eMudhra certificates¶
The faulty eMudhra certificates have been revoked and distruted for all Dataiku Cloud customers.
Applicable to Dataiku Cloud Dedicated Customers¶
Java Base64 memory corruption / CVE-2026-114938¶
For Dataiku Cloud Dedicated customers who are not using API deployments, all updates have been performed, and no further action is required.
For Dataiku Cloud Dedicated customers who are using API deployments, please follow these instructions:
From the deployer, go to each Kubernetes infrastructure. Go to Settings > Sizing and scaling.
In “API node server opts”, add
-XX:-UseBASE64IntrinsicsSave the infrastructure settings
Go to each deployment using this infrastructure, and click “Update”
Necessary updates on the main Dataiku software have already been performed for Cloud Dedicated customers.
Linux TCP use-after-free / CVE-2026-98432¶
All Dataiku Cloud Dedicated customers have already been updated to a non-vulnerable version.
Node.js / Brotli decoder¶
All Dataiku Cloud Dedicated customers have already been updated to a non-vulnerable version.
Oracle Java¶
Dataiku Cloud Dedicated does not use Oracle Java.
eMudhra certificates¶
The faulty eMudhra certificates have been revoked and distruted for all Dataiku Cloud Dedicated customers.
Applicable to Dataiku Cloud Stacks customers¶
General recommendations¶
Given the influx of vulnerabilities, we recommend that you keep watch for OS packages updates, and perform security updates as usual, on a daily basis.
Java Base64 memory corruption / CVE-2026-114938¶
Dataiku Cloud Stacks is affected. While reproduction has not been achieved, it is likely that it is affected pre-authentication, making this vulnerability Critical.
AlmaLinux (the OS used in Dataiku Cloud Stacks) has now released an updated Java package.
Dataiku will release a new version of both Dataiku 14 and Dataiku 15 in the coming days with the up to date package. In the meantime, we strongly recomend that you imediately apply the update.
To update:
DSS and Govern hosts¶
Log onto each host as dataiku user
Run
cd dss_data bin/dss stop
Log onto the host as the centos or ec2-user user
Run
sudo dnf update --security
Then again as the dataiku user
cd dss_data bin/dss start
Fleet Manager¶
Log onto the FM host and switch to the dataiku user
cd /data/dataiku/fmhome/ bin/fm stop
Then, as the centos or ec2-user user
Run
sudo dnf update --security
Then again as the dataiku user
cd /data/dataiku/fmhome/ bin/fm start
API Deployments¶
This section only applies if you have API deployments using Kubernetes.
From the deployer, go to each Kubernetes infrastructure. Go to Settings > Sizing and scaling.
In “API node server opts”, add
-XX:-UseBASE64IntrinsicsSave the infrastructure settings
Go to each deployment using this infrastructure, and click “Update”
Linux TCP use-after-free / CVE-2026-98432¶
Dataiku 14.7.7 and 15.2.2 come with updated kernels. Please update your Dataiku instance to one of these versions or later.
Node.js¶
Dataiku’s use of Node.js is limited. Dataiku has specifically reviewed the vulnerabilities reported in Node.js, notably the Brotli decoder vulnerability and our assessment confirms that Dataiku is not affected by these vulnerabilities.
Nevertheless, Dataiku 14.7.6 and 15.2.1 come with updated versions. Please update your Dataiku instance to one of these versions or later.
You can also manually perform OS package updates.
Brotli decoder¶
Dataiku 14.7.6 and 15.2.1 come with updated versions. Please update your Dataiku instance to one of these versions or later.
You can also manually perform OS package updates.
Oracle Java¶
Dataiku Cloud Stacks does not use Oracle Java.
eMudhra certificates¶
In order to fully distrust the faulty eMudhra certificates, you need to upgrade to one of the Dataiku versions that ship with updated “certifi” Python packages:
If you are running Dataiku version older than 14, no fixed version is available. You need to upgrade. Please note that all versions before Dataiku 14 have reached end of life.
If you are running Dataiku 14, please upgrade to 14.7.6 or above
If you are running Dataiku 15.0, please upgrade to 15.0.3 or above
If you are running Dataiku 15.1 or 15.2, please upgrade to 15.2.1 or above
You should then rebuild code envs, so that other copies of the “certifi” packages are updated.
Applicable to Dataiku Custom Customers¶
General recommendations¶
Given the influx of vulnerabilities, we recommend that you keep watch for OS packages updates, and perform security updates as usual, on a daily basis.
Java Base64 memory corruption / CVE-2026-114938¶
Dataiku Custom is affected. While reproduction has not been achieved, it is likely that it is affected pre-authentication, making this vulnerability Critical.
We strongly recommend that you immediately update Java.
Java is provided by the Customer, and upgrading it is the Customer’s responsibility.
If you are using Java provided by your OS, you will need to follow your OS upgrade instructions. Major OS (notably RedHat, AlmaLinux, RockyLinux and Ubuntu) have now released patched versions.
If you are using Oracle Java, please follow Oracle upgrade instructions. This necessarily requires restarting DSS. If you are using another Java not provided by your OS, please follow the instructions from your Java vendor.
Until the Java update is in place, we strongly recommend that you immediately apply the following mitigation:
DSS¶
Log onto each DSS node as the DSS user and go to the data directory
Run
bin/dss stopEdit the install.ini file and in [javaopts], add the following (if some lines already exist, merge them)
backend.additional.opts = -XX:-UseBASE64Intrinsics eventserver.additional.opts = -XX:-UseBASE64Intrinsics jek.additional.opts = -XX:-UseBASE64Intrinsics fek.additional.opts = -XX:-UseBASE64Intrinsics cak.additional.opts = -XX:-UseBASE64Intrinsics hproxy.additional.opts = -XX:-UseBASE64Intrinsics dku.additional.opts = -XX:-UseBASE64Intrinsics apimain.additional.opts = -XX:-UseBASE64Intrinsics
Run
bin/dssadmin regenerate-config bin/dss start
API nodes¶
API nodes are covered by the above paragraph.
Govern¶
Log onto each Govern node as the Govern user and go to the data directory
Run
bin/dss stopEdit the install.ini file and in [javaopts], add the following (if some lines already exist, merge them)
governserver.additional.opts = -XX:-UseBASE64Intrinsics dku.additional.opts = -XX:-UseBASE64Intrinsics
Run
bin/govern-admin regenerate-config bin/dss start
API Deployments on Kubernetes¶
This section only applies if you have API deployments using Kubernetes.
From the deployer, go to each Kubernetes infrastructure. Go to Settings > Sizing and scaling.
In “API node server opts”, add
-XX:-UseBASE64IntrinsicsSave the infrastructure settings
Go to each deployment using this infrastructure, and click “Update”
Linux TCP use-after-free / CVE-2026-98432¶
The Linux kernel is provided by your OS. Please refer to your OS vendor and perform regular security updates.
Node.js¶
Dataiku’s use of Node.js is limited. Dataiku has specifically reviewed the vulnerabilities reported in Node.js, notably the Brotli decoder vulnerability and our assessment confirms that Dataiku is not affected by these vulnerabilities.
We nevertheless recommend that you perform regular security updates.
Node.js is provided by the Customer, and upgrading it is the Customer’s responsibility.
Please note that this assessment does not extend to the eMudhra certificate issue. Please see below for this one.
Brotli decoder¶
The Brotli decoder (outside of Node.js) is provided by your OS. Please refer to your OS vendor and perform regular security updates.
Oracle Java¶
If you use Oracle Java, you are responsible for upgrading it. Please don’t forget to restart Dataiku after doing so.
eMudhra certificates¶
Please first liaise with your OS provider in order to make sure that you are running updated version of ca-certificates or similar package.
In order to fully distrust the faulty eMudhra certificates, you also need to upgrade to one of the Dataiku versions that ship with updated “certifi” Python packages:
If you are running Dataiku version older than 14, no fixed version is available. You need to upgrade. Please note that all versions before Dataiku 14 have reached end of life.
If you are running Dataiku 14, please upgrade to 14.7.6 or above
If you are running Dataiku 15.0, please upgrade to 15.0.3 or above
If you are running Dataiku 15.1 or 15.2, please upgrade to 15.2.1 or above
You should then rebuild code envs, so that other copies of the “certifi” packages are updated.