pysec-2025-45
Vulnerability from pysec
Published
2025-05-26 07:15
Modified
2025-06-03 17:36
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Details

A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.

Impacted products
Name purl
pypickle pkg:pypi/pypickle
Aliases


To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "pypickle",
        "purl": "pkg:pypi/pypickle"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "14b4cae704a0bb4eb6723e238f25382d847a1917"
            },
            {
              "fixed": "5058ea8c0666b3f8d30893be5c0132ad7fb7bf39"
            }
          ],
          "repo": "https://github.com/erdogant/pypickle",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.0",
        "0.1.1",
        "1.0.0",
        "1.1.0",
        "1.1.1",
        "1.1.3",
        "1.1.4",
        "1.1.5"
      ]
    }
  ],
  "aliases": [
    "CVE-2025-5174"
  ],
  "details": "A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.",
  "id": "PYSEC-2025-45",
  "modified": "2025-06-03T17:36:58.528116+00:00",
  "published": "2025-05-26T07:15:26+00:00",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/erdogant/pypickle/issues/2"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/erdogant/pypickle/issues/2#issuecomment-2889146579"
    },
    {
      "type": "ADVISORY",
      "url": "https://vuldb.com/?ctiid.310262"
    },
    {
      "type": "ADVISORY",
      "url": "https://vuldb.com/?id.310262"
    },
    {
      "type": "ADVISORY",
      "url": "https://vuldb.com/?submit.579157"
    },
    {
      "type": "EVIDENCE",
      "url": "https://github.com/erdogant/pypickle/issues/2"
    },
    {
      "type": "EVIDENCE",
      "url": "https://github.com/erdogant/pypickle/issues/2#issuecomment-2889146579"
    },
    {
      "type": "FIX",
      "url": "https://github.com/erdogant/pypickle/commit/14b4cae704a0bb4eb6723e238f25382d847a1917"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/erdogant/pypickle/issues/2"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/erdogant/pypickle/issues/2#issuecomment-2889146579"
    },
    {
      "type": "WEB",
      "url": "https://github.com/erdogant/pypickle/releases/tag/2.0.0"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?ctiid.310262"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?id.310262"
    },
    {
      "type": "WEB",
      "url": "https://vuldb.com/?submit.579157"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.