FME November 2026 Security Updates | Update 2

Liz Sanderson
Liz Sanderson
  • Updated

Description

This advisory describes security fixes delivered across the FME Platform in November 2026, Update 2. These fixes address vulnerabilities in third-party components bundled with FME as well as vulnerabilities in Safe Software’s own code. No evidence of exploitation of these vulnerabilities in the FME Platform has been observed at the time of publication. 

Safe Software recommends that affected users review the summary table and details below and carry out any necessary actions for your environment.

For the previous security update, see FME November 2026 Security Updates | Update 1

 

Summary Table of Security Updates

Vulnerability ID (CVE) Category Available for Earliest affected FME Version Impact Severity (CVSS Level) Severity (CVSS Score) Resolution
CVE-2026-111497 Third-party (Brotli) FME Engine
FME Form
FME Flow
FME Flow Hosted
2024.2 See Brotli Decoder CVE-2026-111497: Is FME Impacted? 

Critical

(Safe Software rating)

9.3

Upgrade to a fixed version to resolve the core vulnerability:

  • 2026.3.2.0
  • 2026.2.1.3
  • 2026.1.2.2

Follow the applicable workarounds pertaining to DuckDB to mitigate the remaining exposure in the interim.

Various, including  CVE-2026-91403 Third-party (eMudhra intermediate certificate authority (CA) compromise) and related TLS verification fixes FME Engine
FME Form
FME Flow
FME Flow Hosted
No lower limit

The private keys of eight eMudhra intermediate certificate authorities were disclosed in October 2026. An attacker who can intercept network traffic could use them to impersonate any website or service. Web browsers and operating system trust stores have already distrusted these certificates. However, FME ships its own trust stores (the bundled Java runtime, Python certificate bundles, and the HTTP components on macOS and Linux, and the bundled Java and Python certificate lists on all platforms), which still accepted them. Some FME Flow outbound connections and the FME Form-to-Flow connection also did not fully verify TLS certificates. An attacker in that network position could intercept FME's connections to external services and to FME Flow, exposing credentials, OAuth and API tokens, and data in transit. In FME Form, tampered package downloads could also lead to code being run on the user's machine. Exploitation requires the attacker to be able to intercept network traffic.
 

See eMudhra Intermediate CA Compromise: FME Platform Under Investigation

Critical

(Safe Software rating)

9.2

Upgrade to a fixed version:

  • 2026.3.2.0
  • 2026.2.1.3
  • 2026.1.2.2
Pending Information Leak FME Engine
FME Form
FME Flow
FME Flow Hosted
No lower limit

An unauthenticated user of a public FME Flow Workspace App could supply parameter values that cause FME Engine to reveal environment variables from the FME Flow host. Environment variables can contain secrets such as passwords, API keys, or connection strings. FME Flow deployments that publish Workspace Apps without authentication are most exposed. In FME Form, exploitation requires the ability to supply parameter values to the engine.

For more information, see Environment variable expansion (${VAR}) in user parameters in FME 2026.3.1 and late

Critical 9.2

Upgrade to a fixed version:

  • 2026.3.1+ 
  • 2026.2.1.3
  • 2026.1.2.2
Pending OS Command Injection FME Engine
FME Form
FME Flow
FME Flow Hosted
No lower limit A user who can supply a published parameter value to an FME Flow job could bypass FME Engine's input validation and run arbitrary operating system commands, or read arbitrary files, on the engine host with the privileges of the FME Engine service account. This includes unauthenticated users of a public Workspace App or a webhook-triggered Automation. This could result in full compromise of the engine host and the data and credentials available to it. In FME Form, exploitation requires the ability to supply parameter values to the engine. Critical 9.3

Upgrade to a fixed version:

  • 2026.3.1+ 
  • 2026.2.1.3
  • 2026.1.2.2

 

Impact

All FME versions prior to those listed in the table are affected by at least one of these issues. The Brotli decoder vulnerability affects FME 2024.2 and later; the other issues affect all earlier versions. FME 2026.3.1+ already contains fixes for the Information Leak and OS Command Injection vulnerabilities. It remains affected by the Brotli decoder vulnerability (CVE-2026-111497) and by the issues described in the eMudhra row, which include FME’s own TLS certificate verification fixes; upgrading to 2026.3.2.0 resolves these. 
 

Remediation

FME Flow

Please note that due to the technical complexity of these fixes, we are unable to provide manual patches (or instance updates via the FME Flow Hosted UI) that can be applied without reinstalling FME. The only remediation is to upgrade to one of the fixed versions listed in the table above. 

Please visit our Downloads page for the latest installers and refer to our documentation for upgrade instructions for FME Form, FME Flow, and FME Flow Hosted. 

FME Remote Engine(s)

Download FME Remote Engine(s) from our website as normal for any upgrade/install.

FME Flow Hosted

New launchable builds for the fixed versions listed above are being prepared and should be available later on November 19, 2026. FME Flow Hosted customers will be able to upgrade their instances once the builds are listed in the FME Flow Hosted console. This article will be updated when these builds are available. 

FME Flow on Docker or Kubernetes

Upgrade your deployment to one of the fixed versions listed in the summary table by pulling the updated FME Flow images. For Docker, use the Docker Compose file on our Downloads page; for Kubernetes, use the FME Flow Helm charts. See Deploying FME Flow with Docker Compose and Upgrading FME Flow for Kubernetes. 

If you require hands-on assistance to upgrade, we recommend consulting with one of our Partners.

Default Behavior Changes: To address the vulnerabilities, FME Flow in the fixed versions verifies TLS certificates on outbound requests (for example, to remote engines, OAuth providers, licensing services and the URLs that supply dynamic parameters to Flow Apps), and FME Form no longer ignores certificate errors on connections to FME Flow unless certificate verification is turned off for that connection. If a deployment uses self-signed certificates, an internal certificate authority, or a proxy that inspects TLS traffic, these FME Flow requests can fail after the upgrade. To prevent this, add the certificate authority to the Java trust store of the upgraded FME Flow installation. An upgrade replaces the bundled Java runtime, so certificates added before the upgrade are not kept. For remote engines and Flow Apps, administrators can also turn off certificate verification for an individual connection.

 

Workarounds

If you are unable to apply the applicable remediation options listed above, you can limit your risk exposure by applying the mitigations below.

 

Mitigating Brotli Decoder (CVE-2026-111497)

See the mitigation advice shared in Brotli Decoder (CVE-2026-111497): Is FME Impacted? 

Because the DuckDB format embeds its own copy of Brotli and is awaiting an upstream fix, you must follow the workaround in the linked article, in addition to upgrading to a fixed build, to fully mitigate exposure in the interim.

 

Mitigating eMudhra Intermediate CA Compromise (CVE-2026-91403)

We are preparing workarounds for each FME product to help reduce exposure for customers who need time to plan an upgrade. We will publish these in eMudhra Intermediate CA Compromise (CVE-2026-91403): Is FME Impacted? as soon as they are validated, and we will update the article to point to them. In the meantime, please review the recommended precautions in that article and keep operating system trust stores up to date, which protects some FME components. Please note that the trust stores and certificate lists bundled with FME, and the TLS verification fixes in FME Flow and FME Form, can only be fully addressed by upgrading to a fixed build. 

 

General Mitigation Advice

  • Ensure your deployment is locked down from outside access, i.e., internal network only.
  • FME Flow Hosted users may consider using the IP restricting feature on their instances for additional protection.

There may be other mitigations and compensating controls available in your organization, depending on your security posture, defense-in-depth strategies, and configurations of perimeter firewalls and appliance firewalls. All organizations must decide for themselves whether to rely on those protections.

 

Reporting Security Issues

If you believe you have discovered a vulnerability in the FME Platform, our website, or any of our other products, please contact us as quickly as possible at security(at)safe(dot)com, following the guidelines in our Vulnerability Disclosure Policy.

We greatly appreciate the efforts of security researchers and discoverers who share information about potential security issues with us. Your contributions help us to improve our products and better protect our users. 

Please note that while we highly value your contributions, we do not offer compensation for the identification of potential or confirmed security vulnerabilities.
 

Frequently Asked Questions

Why am I receiving a broadcast message?

Safe Software Inc. issues broadcast messages only for critical security updates and advisories that may impact FME Flow deployments. These messages are designed to provide timely and essential information while avoiding unnecessary notifications. Broadcast messages are retrieved via a pull model over HTTPS. Messages are pulled every 12 hours from api.safe.com over HTTPS, ensuring secure retrieval and optimized frequency. See our documentation for more information about Broadcast Messages in FME Flow.

How can I be notified of security updates in the future?

If you would like to be notified of security updates from Safe Software, we encourage you to subscribe to our Security Updates email list by signing up via the form on our Security page.

Why are these security fixes provided as upgrades for FME 2026 only, and not a patch? 

Because of the technical complexity of these security issues, we’re unable to provide a manual patch for this set of fixes. In alignment with our current Product Support Policy, we are delivering these fixes as new builds for the FME 2026.1, 2026.2, and 2026.3 release lines. FME versions released within the past three years remain under technical support: our Customer Support team is happy to assist customers on active maintenance or subscription with any technical issues encountered with upgrading. 
 

Coming soon - Long-term software support for security updates: In response to the significant impact of artificial intelligence (AI) on vulnerability discovery and disclosure cycles, we are currently re-evaluating our Product Support Policy. Our goal is to simplify your experience when choosing which versions to upgrade to and ensure future security updates remain as accessible as possible for specific FME releases. We will soon announce a long-term support (LTS) release of FME that will receive security fixes for an extended period, so staying protected no longer requires a major upgrade each time. We will share further details about eligible FME versions and updates to our Product Support Policy in an upcoming announcement.

 

Support

If you have questions or concerns regarding this advisory, please submit a Support Ticket.

Was this article helpful?

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.