CVE-2025-58058 (GCVE-0-2025-58058)

Vulnerability from cvelistv5 – Published: 2025-08-28 21:54 – Updated: 2025-08-29 13:23
VLAI
Title
github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives
Summary
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14.
Severity
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-08-29 13:22 UTC
CWE
  • CWE-770 - Allocation of Resources Without Limits or Throttling
Assigner
References
Impacted products
Vendor Product Version CPE status
ulikunitz xz Affected: < 0.5.14
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2025-58058",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-08-29T13:22:52.507752Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-08-29T13:23:07.497Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "xz",
          "vendor": "ulikunitz",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.5.14"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn\u0027t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-770",
              "description": "CWE-770: Allocation of Resources Without Limits or Throttling",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-08-28T21:54:05.561Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9"
        },
        {
          "name": "https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2"
        }
      ],
      "source": {
        "advisory": "GHSA-jc7w-c686-c4v9",
        "discovery": "UNKNOWN"
      },
      "title": "github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2025-58058",
    "datePublished": "2025-08-28T21:54:05.561Z",
    "dateReserved": "2025-08-22T14:30:32.221Z",
    "dateUpdated": "2025-08-29T13:23:07.497Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-58058",
      "date": "2026-09-29",
      "epss": "0.00412",
      "percentile": "0.32957"
    },
    "microsoft_vex": {
      "current_release_date": "2026-02-18T14:09:54.000Z",
      "cve": "CVE-2025-58058",
      "id": "msrc_CVE-2025-58058",
      "initial_release_date": "2025-08-02T00:00:00.000Z",
      "product_status:fixed": "20",
      "product_status:known_affected": "28",
      "product_status:known_not_affected": "2",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "github.com/ulikunitz/xz leaks memory when decoding a corrupted multiple LZMA archives",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2025-58058.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "product": "xz",
                "vendor": "ulikunitz",
                "versions": [
                  {
                    "status": "affected",
                    "version": "\u003c 0.5.14"
                  }
                ]
              }
            ],
            "source": "security-advisories@github.com"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn\u0027t include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory allocation has already been done. This issue has been patched in version 0.5.14."
          },
          {
            "lang": "es",
            "value": "xz es un paquete puro de golang para leer y escribir archivos comprimidos xz. Antes de la versi\u00f3n 0.5.14, es posible colocar datos delante de un flujo de bytes codificado en LZMA sin detectar la situaci\u00f3n al leer la cabecera. Esto puede llevar a un mayor consumo de memoria porque la implementaci\u00f3n actual asigna el b\u00fafer de decodificaci\u00f3n completo directamente despu\u00e9s de leer la cabecera. La cabecera LZMA no incluye un n\u00famero m\u00e1gico ni tiene una suma de verificaci\u00f3n para detectar tal problema seg\u00fan la especificaci\u00f3n. Tenga en cuenta que el c\u00f3digo reconoce el problema m\u00e1s tarde al leer el flujo, pero en este momento la asignaci\u00f3n de memoria ya se ha realizado. Este problema ha sido parcheado en la versi\u00f3n 0.5.14."
          }
        ],
        "id": "CVE-2025-58058",
        "lastModified": "2026-09-26T00:10:00.127",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "LOW",
                "baseScore": 5.3,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
                "version": "3.1"
              },
              "exploitabilityScore": 3.9,
              "impactScore": 1.4,
              "source": "security-advisories@github.com",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2025-58058",
                "options": [
                  {
                    "exploitation": "poc"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-08-29T13:22:52.507752Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2025-08-28T22:15:32.577",
        "references": [
          {
            "source": "security-advisories@github.com",
            "url": "https://github.com/ulikunitz/xz/commit/88ddf1d0d98d688db65de034f48960b2760d2ae2"
          },
          {
            "source": "security-advisories@github.com",
            "url": "https://github.com/ulikunitz/xz/security/advisories/GHSA-jc7w-c686-c4v9"
          }
        ],
        "sourceIdentifier": "security-advisories@github.com",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-770"
              }
            ],
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-09-19T12:06:30+00:00",
      "cve": "CVE-2025-58058",
      "id": "CVE-2025-58058",
      "initial_release_date": "2025-08-28T21:54:05.561000+00:00",
      "product_status:fixed": "116",
      "product_status:known_affected": "259",
      "product_status:known_not_affected": "32",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "github.com/ulikunitz/xz: github.com/ulikunitz/xz leaks memory",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-58058.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-23T17:08:51Z",
      "cve": "CVE-2025-58058",
      "id": "CVE-2025-58058",
      "initial_release_date": "2025-08-29T23:23:46Z",
      "product_status:known_affected": "81",
      "product_status:known_not_affected": "284",
      "product_status:recommended": "115",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2025-58058",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2025-58058.json",
      "version": "50"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.