VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

keras: vulnerability history, versions and safety

keras is a package in the Debian ecosystem. Vulert records 25 vulnerabilities for it across 2 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded U25
i
25 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
13 in the last 12 months

Most recent disclosure 10 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all keras vulnerabilities

Vulert verdict on keras i

Updated on 23 Oct 2026

Careful: 25 of the 25 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 25 vulnerabilities on record across 2026 years, 13 in the last year.

What to do: Plan around the 25 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 25 over 2026 years · 13 in the last year i
  • Latest disclosure 10 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 25 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for keras, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.3.1+dfsg-3 U25 No Details →
2.3.1+dfsg2-1 U25 No Details →

Newest 2 of 2 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2024 2
  • 2025 11
  • 2026 11

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 13 of the 25 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for keras

The 5 most severe of 25 vulnerabilities recorded for this package

Search all 25 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Code Execution Vulnerability in Keras Package 9.8 critical No fix published 11 Mar 2025
Critical Security Flaw in Keras Package Allows Arbitrary Code Execution 8.8 high No fix published 13 Apr 2026
Arbitrary Code Execution Vulnerability in Keras 3.14.0 Due to Deserialization Flaw 8.8 high No fix published 03 Jul 2026
Path Traversal Vulnerability in Keras Package Allows Arbitrary File Writes 8.1 high No fix published 11 Jun 2026
Arbitrary Code Execution Vulnerability in Keras: CVE-2025-8747 7.8 high No fix published 11 Aug 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About keras

Is keras safe to use?

Vulert records 25 vulnerabilities for keras in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 25 not yet rated. 25 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does keras have?

25 vulnerabilities are recorded for keras in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 25 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new keras vulnerabilities disclosed?

13 vulnerabilities were recorded for keras in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of keras are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor keras for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the keras version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.