{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2025-15469", "assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "state": "PUBLISHED", "assignerShortName": "openssl", "dateReserved": "2026-01-06T09:27:22.586Z", "datePublished": "2026-01-27T16:01:21.597Z", "dateUpdated": "2026-01-27T16:01:21.597Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "OpenSSL", "vendor": "OpenSSL", "versions": [{"lessThan": "3.6.1", "status": "affected", "version": "3.6.0", "versionType": "semver"}, {"lessThan": "3.5.5", "status": "affected", "version": "3.5.0", "versionType": "semver"}]}], "credits": [{"lang": "en", "type": "reporter", "value": "Stanislav Fort (Aisle Research)"}, {"lang": "en", "type": "remediation developer", "value": "Viktor Dukhovni"}], "datePublic": "2026-01-27T14:00:00.000Z", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "Issue summary: The 'openssl dgst' command-line tool silently truncates input<br>data to 16MB when using one-shot signing algorithms and reports success instead<br>of an error.<br><br>Impact summary: A user signing or verifying files larger than 16MB with<br>one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire<br>file is authenticated while trailing data beyond 16MB remains unauthenticated.<br><br>When the 'openssl dgst' command is used with algorithms that only support<br>one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input<br>is buffered with a 16MB limit. If the input exceeds this limit, the tool<br>silently truncates to the first 16MB and continues without signaling an error,<br>contrary to what the documentation states. This creates an integrity gap where<br>trailing bytes can be modified without detection if both signing and<br>verification are performed using the same affected codepath.<br><br>The issue affects only the command-line tool behavior. Verifiers that process<br>the full message using library APIs will reject the signature, so the risk<br>primarily affects workflows that both sign and verify with the affected<br>'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and<br>library users are unaffected.<br><br>The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the<br>command-line tools are outside the OpenSSL FIPS module boundary.<br><br>OpenSSL 3.5 and 3.6 are vulnerable to this issue.<br><br>OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "value": "Issue summary: The 'openssl dgst' command-line tool silently truncates input\ndata to 16MB when using one-shot signing algorithms and reports success instead\nof an error.\n\nImpact summary: A user signing or verifying files larger than 16MB with\none-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\nfile is authenticated while trailing data beyond 16MB remains unauthenticated.\n\nWhen the 'openssl dgst' command is used with algorithms that only support\none-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\nis buffered with a 16MB limit. If the input exceeds this limit, the tool\nsilently truncates to the first 16MB and continues without signaling an error,\ncontrary to what the documentation states. This creates an integrity gap where\ntrailing bytes can be modified without detection if both signing and\nverification are performed using the same affected codepath.\n\nThe issue affects only the command-line tool behavior. Verifiers that process\nthe full message using library APIs will reject the signature, so the risk\nprimarily affects workflows that both sign and verify with the affected\n'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\nlibrary users are unaffected.\n\nThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\ncommand-line tools are outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.5 and 3.6 are vulnerable to this issue.\n\nOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "metrics": [{"format": "other", "other": {"content": {"text": "Low"}, "type": "https://openssl-library.org/policies/general/security-policy/"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-347", "description": "CWE-347 Improper Verification of Cryptographic Signature", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5", "shortName": "openssl", "dateUpdated": "2026-01-27T16:01:21.597Z"}, "references": [{"name": "OpenSSL Advisory", "tags": ["vendor-advisory"], "url": "https://openssl-library.org/news/secadv/20260127.txt"}, {"name": "3.6.1 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/310f305eb92ea8040d6b3cb75a5feeba8e6acf2f"}, {"name": "3.5.5 git commit", "tags": ["patch"], "url": "https://github.com/openssl/openssl/commit/a7936fa4bd23c906e1955a16a0a0ab39a4953a61"}], "source": {"discovery": "UNKNOWN"}, "title": "'openssl dgst' one-shot codepath silently truncates inputs >16MB", "x_generator": {"engine": "Vulnogram 0.2.0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Issue summary: The 'openssl dgst' command-line tool silently truncates input\ndata to 16MB when using one-shot signing algorithms and reports success instead\nof an error.\n\nImpact summary: A user signing or verifying files larger than 16MB with\none-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire\nfile is authenticated while trailing data beyond 16MB remains unauthenticated.\n\nWhen the 'openssl dgst' command is used with algorithms that only support\none-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input\nis buffered with a 16MB limit. If the input exceeds this limit, the tool\nsilently truncates to the first 16MB and continues without signaling an error,\ncontrary to what the documentation states. This creates an integrity gap where\ntrailing bytes can be modified without detection if both signing and\nverification are performed using the same affected codepath.\n\nThe issue affects only the command-line tool behavior. Verifiers that process\nthe full message using library APIs will reject the signature, so the risk\nprimarily affects workflows that both sign and verify with the affected\n'openssl dgst' command. Streaming digest algorithms for 'openssl dgst' and\nlibrary users are unaffected.\n\nThe FIPS modules in 3.5 and 3.6 are not affected by this issue, as the\ncommand-line tools are outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.5 and 3.6 are vulnerable to this issue.\n\nOpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue."}], "id": "CVE-2025-15469", "lastModified": "2026-01-27T16:16:14.523", "metrics": {}, "published": "2026-01-27T16:16:14.523", "references": [{"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/310f305eb92ea8040d6b3cb75a5feeba8e6acf2f"}, {"source": "openssl-security@openssl.org", "url": "https://github.com/openssl/openssl/commit/a7936fa4bd23c906e1955a16a0a0ab39a4953a61"}, {"source": "openssl-security@openssl.org", "url": "https://openssl-library.org/news/secadv/20260127.txt"}], "sourceIdentifier": "openssl-security@openssl.org", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-347"}], "source": "openssl-security@openssl.org", "type": "Secondary"}]}

{}

{}