Bug 2481891 (CVE-2026-42767) - CVE-2026-42767 openssl: NULL Pointer Dereference in CRMF EncryptedValue Decryption
Summary: CVE-2026-42767 openssl: NULL Pointer Dereference in CRMF EncryptedValue Decry...
Keywords:
Status: NEW
Alias: CVE-2026-42767
Deadline: 2026-06-09
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-27 14:19 UTC by OSIDB Bzimport
Modified: 2026-06-11 12:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:25237 0 None None None 2026-06-11 12:32:02 UTC
Red Hat Product Errata RHSA-2026:25239 0 None None None 2026-06-11 12:34:36 UTC

Description OSIDB Bzimport 2026-05-27 14:19:15 UTC
NULL Pointer Dereference in CRMF EncryptedValue Decryption

NULL Pointer Dereference in CRMF EncryptedValue Decryption (CVE-2026-42767)
Severity: Low

Issue summary: An attacker-controlled CMP (Certificate Management Protocol)
server could trigger a NULL pointer dereference in a CMP client application.

Impact summary: A NULL pointer dereference causes a crash of the
application and a Denial of Service.

An attacker controlling a CMP server (or acting as a man-in-the-middle) could
craft a CMP response containing a CRMF (Certificate Request Message Format)
CertRepMessage with an EncryptedValue structure where the symmAlg field
has an algorithm OID but no parameters field. When the OpenSSL CMP client
processes this response, the NULL dereference occurs, causing a crash of
the CMP client.

Applications that process untrusted CMP/CRMF messages may be affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this
issue, as the affected code is outside the OpenSSL FIPS module boundary.

OpenSSL 4.0, 3.6, and 3.5 are vulnerable to this issue.

OpenSSL 1.0.2, 1.1.1, 3.0, and 3.4 are not affected by this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.1
OpenSSL 3.6 users should upgrade to OpenSSL 3.6.3.
OpenSSL 3.5 users should upgrade to OpenSSL 3.5.7.

This issue was reported by Zhanpeng Liu (Tencent Xuanwu Lab),
Guannan Wang (Tencent Xuanwu Lab) and Guancheng Li (Tencent Xuanwu Lab)
on 27th March 2026. The fix was developed by Igor Ustinov.

Comment 2 errata-xmlrpc 2026-06-11 12:32:00 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:25237 https://access.redhat.com/errata/RHSA-2026:25237

Comment 3 errata-xmlrpc 2026-06-11 12:34:34 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:25239 https://access.redhat.com/errata/RHSA-2026:25239


Note You need to log in before you can comment on or make changes to this bug.