PYSEC-2026-3630

Vulnerability from pysec - Published: 2026-08-10 10:43 - Updated: 2026-08-10 11:01
VLAI
Details

A vulnerability in keras-team/keras version 3.12.0 allows an attacker to craft a malicious tar archive that bypasses the filter_safe_tarinfos validation in keras/src/utils/file_utils.py. Specifically, symlink entries are not subjected to the same is_path_in_dir validation as regular file entries, allowing symlinks to be created outside the intended extraction directory. This can lead to symlink-based file read, file overwrite, or directory escape attacks. The issue is particularly impactful on Python 3.10 and 3.11, where filter_safe_tarinfos is the sole defense against tar path traversal. This vulnerability is distinct from CVE-2025-12060 and other previously reported issues.

Impacted products
Name purl
keras pkg:pypi/keras

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "keras",
        "purl": "pkg:pypi/keras"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.12.3"
            },
            {
              "introduced": "3.13.0"
            },
            {
              "fixed": "3.15.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.2.0",
        "0.3.0",
        "0.3.1",
        "0.3.2",
        "0.3.3",
        "1.0.0",
        "1.0.1",
        "1.0.2",
        "1.0.3",
        "1.0.4",
        "1.0.5",
        "1.0.6",
        "1.0.7",
        "1.0.8",
        "1.1.0",
        "1.1.1",
        "1.1.2",
        "1.2.0",
        "1.2.1",
        "1.2.2",
        "2.0.0",
        "2.0.1",
        "2.0.2",
        "2.0.3",
        "2.0.4",
        "2.0.5",
        "2.0.6",
        "2.0.7",
        "2.0.8",
        "2.0.9",
        "2.1.0",
        "2.1.1",
        "2.1.2",
        "2.1.3",
        "2.1.4",
        "2.1.5",
        "2.1.6",
        "2.10.0",
        "2.10.0rc0",
        "2.10.0rc1",
        "2.11.0",
        "2.11.0rc0",
        "2.11.0rc1",
        "2.11.0rc2",
        "2.11.0rc3",
        "2.12.0",
        "2.12.0rc0",
        "2.12.0rc1",
        "2.13.1",
        "2.13.1rc0",
        "2.13.1rc1",
        "2.14.0",
        "2.14.0rc0",
        "2.15.0",
        "2.15.0rc0",
        "2.15.0rc1",
        "2.2.0",
        "2.2.1",
        "2.2.2",
        "2.2.3",
        "2.2.4",
        "2.2.5",
        "2.3.0",
        "2.3.1",
        "2.4.0",
        "2.4.1",
        "2.4.2",
        "2.4.3",
        "2.5.0rc0",
        "2.6.0",
        "2.6.0rc0",
        "2.6.0rc1",
        "2.6.0rc2",
        "2.6.0rc3",
        "2.7.0",
        "2.7.0rc0",
        "2.7.0rc2",
        "2.8.0",
        "2.8.0rc0",
        "2.8.0rc1",
        "2.9.0",
        "2.9.0rc0",
        "2.9.0rc1",
        "2.9.0rc2",
        "3.0.0",
        "3.0.1",
        "3.0.2",
        "3.0.3",
        "3.0.4",
        "3.0.5",
        "3.1.0",
        "3.1.1",
        "3.10.0",
        "3.11.0",
        "3.11.1",
        "3.11.2",
        "3.11.3",
        "3.12.0",
        "3.12.1",
        "3.12.2",
        "3.13.0",
        "3.13.1",
        "3.13.2",
        "3.14.0",
        "3.14.1",
        "3.2.0",
        "3.2.1",
        "3.3.0",
        "3.3.1",
        "3.3.2",
        "3.3.3",
        "3.4.0",
        "3.4.1",
        "3.5.0",
        "3.6.0",
        "3.7.0",
        "3.8.0",
        "3.9.0",
        "3.9.1",
        "3.9.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-12482",
    "GHSA-58hv-7753-xmfq"
  ],
  "details": "A vulnerability in keras-team/keras version 3.12.0 allows an attacker to craft a malicious tar archive that bypasses the `filter_safe_tarinfos` validation in `keras/src/utils/file_utils.py`. Specifically, symlink entries are not subjected to the same `is_path_in_dir` validation as regular file entries, allowing symlinks to be created outside the intended extraction directory. This can lead to symlink-based file read, file overwrite, or directory escape attacks. The issue is particularly impactful on Python 3.10 and 3.11, where `filter_safe_tarinfos` is the sole defense against tar path traversal. This vulnerability is distinct from CVE-2025-12060 and other previously reported issues.",
  "id": "PYSEC-2026-3630",
  "modified": "2026-08-10T11:01:44.226425Z",
  "published": "2026-08-10T10:43:49.194121Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-12482"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/pull/23015"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/pull/23165"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/commit/9867df45c456dd1077a6243bb56219f66e288150"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/commit/d338a45204bdc787c8b3c4a9b82c1911cd52dedf"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/keras-team/keras"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/releases/tag/v3.12.3"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keras-team/keras/releases/tag/v3.15.0"
    },
    {
      "type": "WEB",
      "url": "https://huntr.com/bounties/5d3638e8-a9f6-4964-a865-ddb9fe4d4b6e"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/keras"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-58hv-7753-xmfq"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Keras: tar extraction permits symlink-based path traversal"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…