Skip to content
Heist/ feed
Back to feed
Medium

picklescan - Security scanning bypass via non-standard file extensions

Type: advisorySources: OSV

picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2025-1716, CVE-2025-1889
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 16:32 UTC · Revision 1

Source evidence

picklescan - Security scanning bypass via non-standard file extensions

core-osv · Original source

Published 3 Mar 2025, 18:38 UTC

picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.

osv:CVE-2025-1889
Complete source record
{
  "id": "78f6165b27e210216bd55624f398f0118e40ea48724760a4a6066d282f421fb8",
  "url": "https://osv.dev/vulnerability/CVE-2025-1889",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "picklescan - Security scanning bypass via non-standard file extensions",
    "summary": "picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.",
    "evidence": "osv:CVE-2025-1889",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2025-1889",
      "aliases": [
        "CVE-2025-1716",
        "CVE-2025-1889",
        "GHSA-655q-fx9r-782v",
        "GHSA-769v-p64c-89pr",
        "PYSEC-2025-18",
        "PYSEC-2025-19"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/mmaitre314/picklescan",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "f34d091824cb8775711f039b5299c277e2ecc663"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0.0.1"
                      },
                      {
                        "last_affected": "0.0.21"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StandardRange"
                  },
                  {
                    "cpe": "cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "fixed": "0.0.22"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v0.0.21",
            "v0.0.20",
            "v0.0.19",
            "v0.0.18",
            "v0.0.17",
            "v0.0.15",
            "v0.0.14",
            "v0.0.13",
            "v0.0.12",
            "v0.0.11",
            "v0.0.10",
            "v0.0.9",
            "v0.0.8",
            "v0.0.7",
            "v0.0.6",
            "v0.0.5",
            "v0.0.4",
            "v0.0.3",
            "v0.0.2"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-1889.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:37.227359032Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1889.json",
        "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-655q-fx9r-782v",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-1889",
        "https://www.sonatype.com/security-advisories/cve-2025-1889",
        "https://github.com/mmaitre314/picklescan",
        "https://pypi.org/project/picklescan/"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-646"
        ],
        "cna_assigner": "Sonatype",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1889.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-1716",
        "evidence": "/aliases"
      },
      {
        "value": "CVE-2025-1889",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 504713,
  "published_at": "2025-03-03T18:38:10.046+00:00"
}