Skip to main content
Public proof of conceptFix available

CVE-2025-69419

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

A public proof of concept exists; no exploitation attested.

  • Published2026-01-27
  • Fixed in3.6.1 · 3.5.5 · 3.4.4 · 3.3.6 · 3.0.19 · 1.1.1ze
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-01-2716:16CVE publishedNVD

Versions per branch

NVD
OpenSSL
BranchAffectedFixed in
3.6≥ 3.6.0, < 3.6.13.6.1
3.5≥ 3.5.0, < 3.5.53.5.5
3.4≥ 3.4.0, < 3.4.43.4.4
3.3≥ 3.3.0, < 3.3.63.3.6
3.0≥ 3.0.0, < 3.0.193.0.19
1.1≥ 1.1.1, < 1.1.1ze1.1.1ze

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As openssl, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • OpenSSLother versions: not affected
    Affected
    • ≥ 3.6.0, < 3.6.1fixed in 3.6.1semver
    • ≥ 3.5.0, < 3.5.5fixed in 3.5.5semver
    • ≥ 3.4.0, < 3.4.4fixed in 3.4.4semver
    • ≥ 3.3.0, < 3.3.6fixed in 3.3.6semver
    • ≥ 3.0.0, < 3.0.19fixed in 3.0.19semver
    • ≥ 1.1.1, < 1.1.1zefixed in 1.1.1zecustom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-01-27

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • compat-openssl11TuxCare:AlmaLinux:9.6all versions · fixed in 1:1.1.1k-5.el9_6.1.tuxcare.els1
  • compat-openssl11TuxCare:AlmaLinux:9.2all versions · fixed in 1:1.1.1k-4.el9_0.tuxcare.els2
  • compat-openssl11Rocky Linux:9all versions · fixed in 1:1.1.1k-5.el9_8.2
  • compat-openssl11Rocky Linux:9all versions · fixed in 1:1.1.1k-5.el9_6.1
  • compat-openssl11Red Hat:rhel_eus:9.6::appstreamall versions · fixed in 1:1.1.1k-5.el9_6.2and 2 other packages
  • compat-openssl11Red Hat:rhel_eus:9.4::appstreamall versions · fixed in 1:1.1.1k-5.el9_4.2and 2 other packages
  • compat-openssl11Red Hat:rhel_e4s:9.2::appstreamall versions · fixed in 1:1.1.1k-4.el9_2.1and 2 other packages
  • compat-openssl11Red Hat:rhel_e4s:9.0::appstreamall versions · fixed in 1:1.1.1k-4.el9_0.1and 2 other packages

180 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-69419 Red Hat Product Security580 products fixed · 5 known affected

    openssl: OpenSSL: Arbitrary code execution due to out-of-bounds write in PKCS#12 processing

    openssl as a component of Red Hat Enterprise Linux 6 · openssl-devel as a component of Red Hat Enterprise Linux 6 · openssl-perl as a component of Red Hat Enterprise Linux 6 · +2 more

  • RHSA-2026:82857 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.18.2

  • RHSA-2026:82372 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.18.2

  • RHSA-2026:82354 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.18.2

  • RHSA-2026:82347 Red Hat Product Security8 products fixed

    Red Hat Security Advisory: cert-manager Operator for Red Hat OpenShift 1.18.2

  • RHSA-2026:19187 Red Hat Product Security16 products fixed

    Red Hat Security Advisory: compat-openssl11 security update

32 more advisories

Full record on NVD

Fix

  1. Update OpenSSL to 3.6.1 · 3.5.5 · 3.4.4 · 3.3.6 · 3.0.19 · 1.1.1ze
  2. Vendor fix Red Hat Product Security RHSA-2026:82857 · 1 productBefore applying this update, make sure all previously released errata relevant to your system have been applied. The steps to apply the upgraded images are different depending on the installation plan approval policy you used when installing the cert-manager Operator for Red Hat OpenShift. - If t…
  3. Vendor fix Red Hat Product Security RHSA-2026:19187 · 16 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  4. Vendor fix Red Hat Product Security RHSA-2026:14773 · 4 productsFor OpenShift Container Platform 4.15 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  5. Vendor fix Red Hat Product Security RHSA-2026:15087 · 4 productsFor OpenShift Container Platform 4.14 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  6. Vendor fix Red Hat Product Security RHSA-2026:7239 · 1 productFor OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.…
  7. Vendor fix Red Hat Product Security RHSA-2026:7261 · 13 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2026-01-27
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-x77r-97gw-wh89

Frequently asked questions

What is 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 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.

Is CVE-2025-69419 actively exploited?

Active exploitation of CVE-2025-69419 has not been confirmed. Its EPSS score was 0.6% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-69419?

CVE-2025-69419 has a CVSS v3 base score of 7.4 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record