ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-69419

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 tr

Published Jan 27, 2026 · catalog updated Oct 15, 2026 · Issue summary: Calling PKCS12_get_friendlyname()

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-69419. EPSS is 0.61%. Act only if a listed version of Issue summary: Calling PKCS12_get_friendlyname() is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Issue summary: Calling PKCS12_get_friendlyname()).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.61%
Remediation
Version ranges on file
Affected products
cpe openssl/openssl · vendor OpenSSL OpenSSL 3.0.0 <3.0.19

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe openssl/openssl< 1.1.1ze
  • cpe openssl/openssl< 3.0.19
  • cpe openssl/openssl< 3.3.6
  • cpe openssl/openssl< 3.4.4
  • cpe openssl/openssl< 3.5.5
  • cpe openssl/openssl< 3.6.1
  • vendor OpenSSL OpenSSL 3.0.0 <3.0.193.0.0 <3.0.19

How to fix CVE-2025-69419

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-69419. EPSS is 0.61%. Act only if a listed version of Issue summary: Calling PKCS12_get_friendlyname() is installed.

Which versions are affected?

Compare what you have installed with OpenSSL OpenSSL 3.0.0 <3.0.19 3.0.0 <3.0.19. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-787: Out-of-bounds Write. EPSS 0.61%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OpenSSL security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 27, 2026 · EUVD

    Detected

    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

  2. Oct 15, 2026 · EUVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2025-69419

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-69419

    30-day exploitation probability 0.61%

    first.org
  • EUVDVulnerability recordEUVD-2025-206395

    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 caus

    euvd.enisa.europa.eu
  • Monitored products — criticalVendor advisoryCVE-2025-69419

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 5, 2026
  • Monitored products — criticalNov 4, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 2, 2026