# CVE-2025-69419: Out of bounds write in PKCS12_get_friendlyname() UTF-8 conversion > Attackers can cause denial of service via out-of-bounds write in OpenSSL when parsing malicious PKCS#12 files with specific UTF-16 strings. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Jan 2026 - **Updated:** 15 Oct 2026 - **Also known as:** ALPINE-CVE-2025-69419, ALSA-2026:19187, ALSA-2026:3042, ALSA-2026:4472, AZL-75290, AZL-75786, AZL-75890, AZL-76116, AZL-76152, AZL-78573, BELL-CVE-2025-69419, CLEANSTART-2026-MH21878, CLSA-2026-1771237525, CLSA-2026-1771955371, CLSA-2026-1772098723, CLSA-2026-1772102739, CLSA-2026-1773669005, CLSA-2026-1773999595, DEBIAN-CVE-2025-69419, ECHO-1956-f8c5-351f, GHSA-x77r-97gw-wh89, JLSEC-2026-263, MINI-4h82-h65g-rf76, MINI-f3m8-v4hf-jr2m, MINI-f9qm-gx9g-pp9f, OESA-2026-1612, OESA-2026-1614, OESA-2026-1615, OESA-2026-1661, OESA-2026-1662, OESA-2026-1664, RHSA-2026:19187, RHSA-2026:3042, RHSA-2026:3364, RHSA-2026:3437, RHSA-2026:4163, RHSA-2026:4214, RHSA-2026:4472, RHSA-2026:4824, RHSA-2026:4825, RHSA-2026:5214, RHSA-2026:5217, RLSA-2026:19187, RLSA-2026:3042, RLSA-2026:4472, ROOT-OS-ALPINE-315-CVE-2025-69419, UBUNTU-CVE-2025-69419 ## What is CVE-2025-69419? CVE-2025-69419 is a high-severity memory corruption vulnerability in Openssl Openssl, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2025-69419? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openssl` | AlmaLinux:8 | All versions | 1:1.1.1k-15.el8_6 | | `openssl-devel` | AlmaLinux:8 | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs` | AlmaLinux:8 | All versions | 1:1.1.1k-15.el8_6 | | `openssl-perl` | AlmaLinux:8 | All versions | 1:1.1.1k-15.el8_6 | | `compat-openssl11` | AlmaLinux:9 | All versions | 1:1.1.1k-5.el9_7.1 | | `compat-openssl11` | AlmaLinux:9 | All versions | 1:1.1.1k-5.el9_8.2 | | `openssl` | Red Hat:enterprise_linux:8::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-perl` | Red Hat:enterprise_linux:8::baseos | All versions | 1:1.1.1k-15.el8_6 | | `compat-openssl11` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_7.1 | | `compat-openssl11` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_8.2 | | `compat-openssl11-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_7.1 | | `compat-openssl11-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_8.2 | | `compat-openssl11-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_7.1 | | `compat-openssl11-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.1.1k-5.el9_8.2 | | `openssl` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-devel` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-libs` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-libs-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl-perl` | Red Hat:rhel_aus:8.2::baseos | All versions | 1:1.1.1c-21.el8_2.2 | | `openssl` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-devel` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-libs` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-libs-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl-perl` | Red Hat:rhel_aus:8.4::baseos | All versions | 1:1.1.1g-18.el8_4.2 | | `openssl` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-devel` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-perl` | Red Hat:rhel_aus:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-devel` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | | `openssl-libs-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 1:1.1.1k-15.el8_6 | Products: Openssl Openssl. ## How do I fix CVE-2025-69419? Apply the vendor's patch. ## Is CVE-2025-69419 being exploited? There is no known exploitation of CVE-2025-69419 in the wild and no public exploit code. Public exploit code: - https://github.com/Kha-Beleh/PoC-CVE-2025-69419 (github_poc): https://github.com/Kha-Beleh/PoC-CVE-2025-69419 ## Other vulnerabilities in Openssl Openssl - [CVE-2009-3245](https://insights.sbomify.com/CVE-2009-3245/): Null dereference in n/a (critical 10.0) - [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0) - [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8) - [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8) - [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-69419 and fix it if it is affected. What it is: CVE-2025-69419 is a high-severity memory corruption vulnerability in Openssl Openssl, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-69419 in the wild and no public exploit code. Affected product: Openssl Openssl. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-69419/ (Markdown: https://insights.sbomify.com/CVE-2025-69419/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-69419 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-69419 - OSV: https://osv.dev/vulnerability/CVE-2025-69419 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-69419/ Summaries are generated and may contain mistakes; the official description above is the record.