Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-12484Published 2026-07-19

CVE-2026-12484 — keras-team keras-team/keras

high

As of 2026-07-20, CVE-2026-12484 is a HIGH-severity vulnerability in keras-team keras-team/keras, CVSS v3.1 7.8, EPSS 0.2% (10.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-12484 as of 2026-07-20; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.8/10High
EPSS
0.2%Higher than 10.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.3/10Threadlinqs triage score
Published
Updated 2026-07-20
CVSS v3.1 7.8 (HIGH) · EPSS 0.2% (higher than 10.5% of all scored CVEs) · Priority 4.3/10 · Published 2026-07-19

Last updated:

What is CVE-2026-12484?

A vulnerability in keras-team/keras version 3.15.0 allows unsafe deserialization of attacker-controlled PyTorch pickle data through the public `keras.layers.TorchModuleWrapper.from_config` method. This method invokes `torch.load(..., weights_only=False)` without requiring an explicit unsafe opt-in, such as a `safe_mode=False` parameter. When called outside a `SafeModeScope(True)` context, the absence of an ambient safe mode state permits unsafe deserialization by default. This issue can lead to arbitrary code execution if untrusted Keras layer configurations are processed using this method. The vulnerability arises because the method does not enforce safe deserialization practices unless explicitly guarded by Keras safe mode.

The record classifies CVE-2026-12484 under weakness class CWE-502. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 78 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.8 — HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 10.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-19, last modified 2026-07-20

Is CVE-2026-12484 being exploited?

It currently carries a trending score of 32 in the Threadlinqs vulnerability feed.

Affected products and versions

  • keras-team: keras-team/keras

How to fix CVE-2026-12484

No vendor patch reference has been recorded for CVE-2026-12484 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-12484

No threat campaign in the Threadlinqs corpus currently references CVE-2026-12484, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Other references