FKIE_CVE-2025-15469

Vulnerability from fkie_nvd - Published: 2026-01-27 16:16 - Updated: 2026-02-02 18:37
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Summary
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.
References
openssl-security@openssl.orghttps://github.com/openssl/openssl/commit/310f305eb92ea8040d6b3cb75a5feeba8e6acf2fPatch
openssl-security@openssl.orghttps://github.com/openssl/openssl/commit/a7936fa4bd23c906e1955a16a0a0ab39a4953a61Patch
openssl-security@openssl.orghttps://openssl-library.org/news/secadv/20260127.txtVendor Advisory
Impacted products
Vendor Product Version
openssl openssl *
openssl openssl *
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "1CAC7CBE-EC03-4089-938A-0CEEB2E09B62",
              "versionEndExcluding": "3.5.5",
              "versionStartIncluding": "3.5.0",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "68352537-5E99-4F4D-B78A-BCF0353A70A5",
              "versionEndExcluding": "3.6.1",
              "versionStartIncluding": "3.6.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Issue summary: The \u0027openssl dgst\u0027 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 \u0027openssl dgst\u0027 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\u0027openssl dgst\u0027 command. Streaming digest algorithms for \u0027openssl dgst\u0027 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."
    },
    {
      "lang": "es",
      "value": "Resumen del problema: La herramienta de l\u00ednea de comandos \u0027openssl dgst\u0027 trunca silenciosamente los datos de entrada a 16MB cuando se utilizan algoritmos de firma de un solo paso e informa \u00e9xito en lugar de un error.\n\nResumen del impacto: Un usuario que firma o verifica archivos de m\u00e1s de 16MB con algoritmos de un solo paso (como Ed25519, Ed448 o ML-DSA) puede creer que el archivo completo est\u00e1 autenticado mientras que los datos finales m\u00e1s all\u00e1 de 16MB permanecen sin autenticar.\n\nCuando se utiliza el comando \u0027openssl dgst\u0027 con algoritmos que solo admiten la firma de un solo paso (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), la entrada se almacena en b\u00fafer con un l\u00edmite de 16MB. Si la entrada excede este l\u00edmite, la herramienta trunca silenciosamente a los primeros 16MB y contin\u00faa sin se\u00f1alar un error, contrario a lo que establece la documentaci\u00f3n. Esto crea una brecha de integridad donde los bytes finales pueden modificarse sin detecci\u00f3n si tanto la firma como la verificaci\u00f3n se realizan utilizando la misma ruta de c\u00f3digo afectada.\n\nEl problema afecta solo el comportamiento de la herramienta de l\u00ednea de comandos. Los verificadores que procesan el mensaje completo utilizando las API de la librer\u00eda rechazar\u00e1n la firma, por lo que el riesgo afecta principalmente a los flujos de trabajo que tanto firman como verifican con el comando \u0027openssl dgst\u0027 afectado. Los algoritmos de resumen por streaming para \u0027openssl dgst\u0027 y los usuarios de la librer\u00eda no se ven afectados.\n\nLos m\u00f3dulos FIPS en 3.5 y 3.6 no se ven afectados por este problema, ya que las herramientas de l\u00ednea de comandos est\u00e1n fuera del l\u00edmite del m\u00f3dulo FIPS de OpenSSL.\n\nOpenSSL 3.5 y 3.6 son vulnerables a este problema.\n\nOpenSSL 3.4, 3.3, 3.0, 1.1.1 y 1.0.2 no se ven afectados por este problema."
    }
  ],
  "id": "CVE-2025-15469",
  "lastModified": "2026-02-02T18:37:39.313",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "NONE",
          "baseScore": 5.5,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-01-27T16:16:14.523",
  "references": [
    {
      "source": "openssl-security@openssl.org",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/openssl/openssl/commit/310f305eb92ea8040d6b3cb75a5feeba8e6acf2f"
    },
    {
      "source": "openssl-security@openssl.org",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/openssl/openssl/commit/a7936fa4bd23c906e1955a16a0a0ab39a4953a61"
    },
    {
      "source": "openssl-security@openssl.org",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://openssl-library.org/news/secadv/20260127.txt"
    }
  ],
  "sourceIdentifier": "openssl-security@openssl.org",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-347"
        }
      ],
      "source": "openssl-security@openssl.org",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.