CVE-2026-12482

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-14) is not newer than that change (2026-10-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-43620 (ENISA EUVD) · GHSA-58hv-7753-xmfq (GitHub Security Advisories) · PYSEC-2026-3630 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 24, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
Patch available.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/5d3638e8-a9f6-4964-a865-ddb9fe4d4b6e

Vendor Advisories for CVE-2026-12482(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipkeras @ 3.12.3 (fixes < 3.12.3)—ghsa
pipkeras @ 3.15.0 (fixes >= 3.13.0, < 3.15.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
keras2.3.1+dfsg-3, 2.3.1+dfsg2-1
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
keras0.2.0 ... 3.9.2 (120 versions)
  • every version up to 3.12.3: fixed in 3.12.3
  • 3.13.0 up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 161 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 61 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-11-07 19:47 UTCGHSA enrichmentGHSA-58hv-7753-xmfq · GitHub severity LOW · GitHub CVSS 3.1
  7. 2026-11-07 19:47 UTCEchelonGraph re-scored
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-25 14:49 UTCEchelonGraph re-scored
  23. 2026-10-24 22:28 UTCEchelonGraph re-scored
  24. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 75 more
  1. 2026-10-23 07:17 UTCEchelonGraph re-scored
  2. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-18 05:04 UTCEchelonGraph re-scored
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-12 16:36 UTCEchelonGraph re-scored
  14. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-10-11 20:12 UTCEchelonGraph re-scored
  16. 2026-10-11 18:24 UTCEchelonGraph re-scored
  17. 2026-10-11 14:57 UTCEchelonGraph re-scored
  18. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  26. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-10-01 13:30 UTCEchelonGraph re-scored
  29. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  31. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-28 09:24 UTCEchelonGraph re-scored
  33. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  34. 2026-09-24 09:57 UTCEchelonGraph re-scored
  35. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-09-23 04:15 UTCEchelonGraph re-scored
  37. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  38. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  39. 2026-09-18 04:58 UTCEchelonGraph re-scored
  40. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-14 07:25 UTCEchelonGraph re-scored
  42. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-09-13 07:56 UTCEchelonGraph re-scored
  44. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-09-12 01:48 UTCEchelonGraph re-scored
  46. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-09-08 01:50 UTCEchelonGraph re-scored
  50. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-09-05 21:20 UTCEchelonGraph re-scored
  53. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  54. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  57. 2026-08-31 05:50 UTCEchelonGraph re-scored
  58. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  59. 2026-08-30 05:26 UTCEchelonGraph re-scored
  60. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-08-28 02:29 UTCEchelonGraph re-scored
  63. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-08-27 01:32 UTCEchelonGraph re-scored
  65. 2026-08-26 02:04 UTCEchelonGraph re-scored
  66. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  67. 2026-08-24 22:34 UTCEchelonGraph re-scored
  68. 2026-08-23 23:04 UTCEchelonGraph re-scored
  69. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  70. 2026-08-22 23:05 UTCEchelonGraph re-scored
  71. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  72. 2026-08-21 00:09 UTCEchelonGraph re-scored
  73. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  74. 2026-08-20 00:40 UTCEchelonGraph re-scored
  75. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 15th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-12482?
CVE-2026-12482 is a medium-severity vulnerability; its CVE record was published on July 14, 2026. 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,…
When was the CVE record for CVE-2026-12482 published?
The CVE record for CVE-2026-12482 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-12482 actively exploited?
CVE-2026-12482 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12482?
CVE-2026-12482 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-12482?
A fix for CVE-2026-12482 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-12482 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12482

Explore →

Is Your Infrastructure Affected by CVE-2026-12482?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs