JLSEC-2026-258
- Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/blob/main/advisories/published/2026/JLSEC-2026-258.md
- Import Source
- https://github.com/JuliaLang/SecurityAdvisories.jl/tree/generated/osv/2026/JLSEC-2026-258.json
- JSON Data
- https://api.osv.dev/v1/vulns/JLSEC-2026-258
- Upstream
- Published
- 2026-04-27T18:33:55.942Z
- Modified
- 2026-04-27T19:02:38.877578472Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N CVSS Calculator
- Summary
- Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when...
- Details
-
Issue summary: The 'openssl dgst' command-line tool silently truncates input data to 16MB when using one-shot signing algorithms and reports success instead of an error.
Impact summary: A user signing or verifying files larger than 16MB with one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire file is authenticated while trailing data beyond 16MB remains unauthenticated.
When the 'openssl dgst' command is used with algorithms that only support one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input is buffered with a 16MB limit. If the input exceeds this limit, the tool silently truncates to the first 16MB and continues without signaling an error, contrary to what the documentation states. This creates an integrity gap where trailing bytes can be modified without detection if both signing and verification are performed using the same affected codepath.
The issue affects only the command-line tool behavior. Verifiers that process the full message using library APIs will reject the signature, so the risk primarily affects workflows that both sign and verify with the affected 'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and library users are unaffected.
The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the command-line tools are outside the OpenSSL FIPS module boundary.
OpenSSL 3.5 and 3.6 are vulnerable to this issue.
OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.
- Database specific
{ "sources": [ { "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2025-15469", "database_specific": { "status": "Analyzed" }, "html_url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15469", "modified": "2026-02-02T18:37:39.313Z", "id": "CVE-2025-15469", "imported": "2026-04-27T16:32:48.477Z", "published": "2026-01-27T16:16:14.523Z" }, { "url": "https://api.github.com/advisories/GHSA-v2vr-926q-29fr", "html_url": "https://github.com/advisories/GHSA-v2vr-926q-29fr", "modified": "2026-01-29T15:31:31Z", "id": "GHSA-v2vr-926q-29fr", "imported": "2026-04-27T16:34:09.420Z", "published": "2026-01-27T18:32:15Z" }, { "url": "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2025-206399", "html_url": "https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-206399", "modified": "2026-01-29T14:54:35Z", "id": "EUVD-2025-206399", "imported": "2026-04-27T16:33:07.330Z", "published": "2026-01-27T16:01:21Z" } ], "license": "CC-BY-4.0" }- References
-
- https://github.com/advisories/GHSA-v2vr-926q-29fr
- https://github.com/openssl/openssl/commit/310f305eb92ea8040d6b3cb75a5feeba8e6acf2f
- https://github.com/openssl/openssl/commit/a7936fa4bd23c906e1955a16a0a0ab39a4953a61
- https://nvd.nist.gov/vuln/detail/CVE-2025-15469
- https://openssl-library.org/news/secadv/20260127.txt