Silverblaze
Silverblaze Security Bulletin – CVE-2026-119618

Security advisories

Security Bulletin: Apache HTTP Server HTTP/2 Vulnerability
CVE-2026-119618

Published November 13, 2026 · Updated November 20, 2026
Not affected
Status: Not affected in Silverblaze standard configurations.
Where the issue is: Third-party: Apache HTTP Server
Silverblaze Cloud-hostedCustomer-managed
Silverblaze PortalNot affected
No action required.
Not affected
We recommend verifying your Apache configuration.
SmartFormsNot applicableNot affected
We recommend verifying your Apache configuration.
Silverblaze ACE
Multi-tenant SaaS on Microsoft Azure
Not affected
Does not use Apache HTTP Server.
Not applicable

Summary

On November 12, 2026, a critical vulnerability (CVE-2026-119618) was disclosed in the HTTP/2 module (mod_http2) of the Apache HTTP Server. On affected servers, an unauthenticated remote attacker could potentially execute code. The issue is in the Apache web server, not in the Silverblaze Portal, SmartForms, or Apache Tomcat.

Assessment

A server is only affected if the Apache HTTP/2 module is loaded. The Silverblaze standard Apache configuration, for both the Silverblaze Portal and SmartForms, does not load this module. Silverblaze Cloud-hosted environments, where we manage the web server and its patching for you, have been confirmed not affected. Environments managed by your own IT team, on-premise or in your own cloud, are most likely not affected. Because configurations can change over time, we recommend your IT team verify this using the steps below.

Silverblaze ACE does not use the Apache HTTP Server and is not affected.

How to Check (customer-managed environments)

On the server running Apache, open a command prompt in the Apache bin folder and run:

If there is no output, the server is not affected and no action is needed.

If the Module Is Listed

  1. In the Apache configuration file (usually conf\httpd.conf), add # to the start of the line LoadModule http2_module modules/mod_http2.so.
  2. Run httpd -t and confirm it reports Syntax OK.
  3. Restart the Apache service. This briefly interrupts the portal, so schedule it accordingly.
  4. Run the check again and confirm there is no output.

Browsers switch to HTTP/1.1 automatically with no noticeable impact. Once a fixed Apache version is released, we recommend updating Apache as part of your regular patching.

Revision History

Questions

Customers with questions about this bulletin, or who need help with any steps above, can email support@silverblaze.com. We continue to monitor disclosed vulnerabilities and will publish an advisory promptly if any are found to affect Silverblaze products.