CVE-2025-49600: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-r3gf-c2cf-vp8q
Share
CVSS 4.9
CWE-325
Published
Advisory Summary

CVE-2025-49600 is a MODERATE (CVSS 4.9) security vulnerability vulnerability (CWE-325: Missing Cryptographic Step) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.. Remediation is available in the latest vendor maintenance releases.

CVE-2025-49600 at a Glance

CVE Identifier CVE-2025-49600
GHSA Identifier GHSA-r3gf-c2cf-vp8q
Severity MODERATE
CVSS v3.1 Base Score 4.9
CWE Classification CWE-325: Missing Cryptographic Step
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 4.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N).

Attack Vector Physical (AV:P)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-49600

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-49600, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-325: Missing Cryptographic Step, where the product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.

References

NVD — CVE-2025-49600 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-49600
Software Source Repository REPOSITORY
https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-3.md

Frequently Asked Questions

What is CVE-2025-49600?
CVE-2025-49600 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-325: Missing Cryptographic Step.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2025-49600?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2025-49600?
CVE-2025-49600 has a CVSS v3.1 base score of 4.9 (MODERATE) with vector string CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N.
What CWE is associated with CVE-2025-49600?
CVE-2025-49600 is classified under CWE-325: Missing Cryptographic Step (The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.).
How can I check Maven dependencies for CVE-2025-49600?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r3gf-c2cf-vp8q",
  "modified" : "2025-07-04T15:31:10Z",
  "published" : "2025-07-04T15:31:10Z",
  "aliases" : [ "CVE-2025-49600" ],
  "details" : "In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault injection against the accelerator to bypass verification.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-49600"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-3.md"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-325" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-07-04T15:15:22Z"
  }
}