CVE-2024-3660
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA arbitrary code injection vulnerability in TensorFlow's Keras framework (<2.13) allows attackers to execute arbitrary code with the same permissions as the application using a model that allow arbitrary code irrespective of the application.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceArbitrary code injection vulnerability in TensorFlow's Keras framework versions prior to 2.13 allows attackers to execute arbitrary code through malicious models. The vulnerability permits code execution with the same privileges as the application loading the model, making it highly severe.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.13.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Keras versionRun 'pip show keras' or execute 'python -c "import keras; print(keras.__version__)"' to determine the currently installed Keras versionAffected if The installed version is lower than 2.13.1
-
Verify TensorFlow bundled Keras versionCheck tensorflow.keras version by running 'python -c "import tensorflow as tf; print(tf.keras.__version__)"'Affected if The TensorFlow bundled Keras version is lower than 2.13.1
-
Audit model loading codeSearch codebase for keras.models.load_model, keras.models.model_from_json, tf.keras.models.load_model, pickle usage with model objects, or tf.keras.models.model_from_config callsAffected if Code loads models from untrusted or external sources without validation
-
Review model input sourcesIdentify all entry points where model files or serialized model data are loaded, including file uploads, network downloads, or deserialization of model objectsAffected if Models are loaded from untrusted or external sources without strict validation
System is affected if Keras version is below 2.13.1 AND the application loads or deserializes models from untrusted or external sources
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.13.1
Upgrade to Keras 2.13 or later. If immediate upgrade is not possible, avoid loading untrusted models and implement strict model validation before loading.
Keras 2.13.1 or later
- Check the current Keras version by running: pip show keras
- Upgrade Keras to version 2.13.1 or later using: pip install --upgrade keras>=2.13.1
- Verify the installation was successful: pip show keras
- If using TensorFlow, ensure TensorFlow is also compatible with the new Keras version
- Test that applications using Keras models function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3660 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data