CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.6%

EPSS score, percentile 49 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

7.4 High

CVSS v3.1 base score, from CISA's enrichment of the record

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (6)

Which versions are affected?

Affected

• from 3.6.0 to before 3.6.1
• from 3.5.0 to before 3.5.5
• from 3.4.0 to before 3.4.4
• from 3.3.0 to before 3.3.6
• from 3.0.0 to before 3.0.19
• from 1.1.1 to before 1.1.1ze

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Advisories and patches

• 3.6.1 git commit (Patch)
• 3.5.5 git commit (Patch)
• 3.4.4 git commit (Patch)
• 3.3.6 git commit (Patch)
• 3.0.19 git commit (Patch)
• OpenSSL Advisory (Vendor advisory)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Versions not listed are: unaffected.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() funct…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2025-69419 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 27 Jan 2026.
• The CVE record carries a CVSS v3.1 base score of 7.4 (High), taken from CISA's enrichment of the record.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.6% (percentile 49), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact total.
• The credits in the CVE record name AISLE as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion

Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer. The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline

Known exploited OpenSSL vulnerabilities

• CVE-2014-0160: OpenSSL Information Disclosure Vulnerability (added 4 May 2022)