Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

OpenSSL ASN.1 Multibyte String Conversion Heap Buffer Overflow

IdentifiersCVE-2026-7383CWE-190

CVE-2026-7383 is a low-severity memory corruption vulnerability in OpenSSL's ASN.1 multibyte string conversion logic, specifically in ASN1_mbstring_copy() and ASN1_mbstring_ncopy(). When producing Unicode output, the code computes the destination buffer size in a signed int. For BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), the size is derived by left-shifting the input character count; for UTF8STRING, it is derived by summing per-character byte counts. With extremely large attacker-controlled input, approximately on the order of 2^30 characters, these calculations can overflow the signed integer used for sizing. In the worst case, such as UNIVERSALSTRING input near 2^30 characters, the computed size can wrap to zero, causing OPENSSL_malloc(1) to allocate a one-byte buffer, after which the subsequent copy operation writes far beyond the allocation, resulting in a heap buffer overflow. OpenSSL states that normal X.509 certificate processing does not reach this condition because ASN1_STRING_set_by_NID() applies DIRSTRING_TYPE restrictions that exclude UNIVERSALSTRING and enforces per-NID size limits. Exploitation therefore depends on application-specific use of the affected APIs or custom ASN.1 string type registration via ASN1_STRING_TABLE_add().

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause a heap buffer overflow leading to process crash, memory corruption, undefined behavior, and potentially attacker-controlled code execution. OpenSSL assessed the issue as low severity because standard certificate-handling and network protocol paths do not exercise the vulnerable condition, and exploitation requires unusually large attacker-controlled input and non-default application usage of the affected ASN.1 string conversion routines.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, avoid passing attacker-controlled data to ASN1_mbstring_copy() and ASN1_mbstring_ncopy(), especially very large multibyte string inputs. Do not expose custom ASN.1 string type handling registered via ASN1_STRING_TABLE_add() to untrusted input. Enforce strict upper bounds on input size well below the overflow threshold. Standard X.509 certificate processing paths are stated not to trigger this issue.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed OpenSSL release that includes the CVE-2026-7383 patch. Downstream distributions have shipped fixes in their updated OpenSSL packages. In addition to patching, review application code for direct use of ASN1_mbstring_copy(), ASN1_mbstring_ncopy(), or custom ASN.1 string table registration through ASN1_STRING_TABLE_add(), and ensure untrusted input lengths are bounded before invoking these APIs.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication
OpenSSL Software FoundationOpensslapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity19

Community discussion across Reddit, Mastodon, and other social sources.