CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-31790 remediation guide

OpenSSL OpenSSL, SIMATIC CN 4100, openssl

Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set t...

Open CVE record
ProductOpenSSL OpenSSL, SIMATIC CN 4100, openssl
Affected versions>= 3.6.0 < 3.6.2, >= 3.5.0 < 3.5.6, >= 3.4.0 < 3.4.5, >= 3.3.0 < 3.3.7, >= 3.0.0 < 3.0.20, < V5.0
Fixed versions3.0.20, 3.3.7, 3.4.5, 3.5.6, 3.6.2
Priority basisReview · CVSS 7.5 · EPSS 1.20%
01

Identify the affected asset

Confirm whether OpenSSL OpenSSL, SIMATIC CN 4100, openssl is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 3.6.0 < 3.6.2, >= 3.5.0 < 3.5.6, >= 3.4.0 < 3.4.5, >= 3.3.0 < 3.3.7, >= 3.0.0 < 3.0.20, < V5.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 3.0.20, 3.3.7, 3.4.5, 3.5.6, 3.6.2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-31790 Remediation Guide | SECUFOCUS NOW