CVE-2026-62997

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kedro-Datasets provides data connectors for Kedro. From version 5.0.0 until 9.5.0, kedro_datasets_experimental.pytorch.PyTorchDataset in kedro-datasets loads .pt model files with torch.load without enforcing weights_only=True, and user-supplied load_args are silently dropped. On PyTorch versions earlier than 2.6, a malicious pickle-backed model from an attacker-influenced shared registry, downloaded checkpoint, or partitioned external source can execute arbitrary code when a Kedro pipeline loads it. The issue affects only the opt-in kedro_datasets_experimental component and does not affect users who load only trusted files. This issue is fixed in version 9.5.0.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

kedro-datasets-9.5.0

Patch available: kedro-org/kedro-plugins kedro-datasets-9.5.0

https://github.com/kedro-org/kedro-plugins/releases/tag/kedro-datasets-9.5.0
github_commit Patch Available

commit 4d6deb7a7ecb (kedro-org/kedro-plugins)

Patch available: kedro-org/kedro-plugins kedro-datasets-9.5.0 (contains commit 4d6deb7a7ecb)

https://github.com/kedro-org/kedro-plugins/commit/4d6deb7a7ecba483d33fd43e2a6c063bcf22f413
github_pr Patch Available

fix(datasets): harden experimental PyTorchDataset against unsafe torch.load

Patch available: kedro-org/kedro-plugins kedro-datasets-9.5.0 (PR #1433 merged 2026-06-29)

https://github.com/kedro-org/kedro-plugins/pull/1433
generic

(security) Security Vulnerability · Issue #1431 · kedro-org/kedro-plugins · GitHub

https://github.com/kedro-org/kedro-plugins/issues/1431
github Patch Available

(experimental) Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load` · Advisory · kedro-org/kedro-plugins · GitHub

https://github.com/kedro-org/kedro-plugins/security/advisories/GHSA-f9q4-h45w-jrrq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 22:21 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 20:01 UTCEG score recompute
  4. 2026-09-19 06:51 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 04:32 UTCEG score recompute
  7. 2026-09-17 15:23 UTCEG score recompute
  8. 2026-09-17 15:04 UTCEG score recompute
  9. 2026-09-16 21:23 UTCEG score recompute
  10. 2026-09-16 21:00 UTCEG score recompute
  11. 2026-09-16 20:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62997?
CVE-2026-62997 is a high vulnerability published on September 16, 2026. Kedro-Datasets provides data connectors for Kedro. From version 5.0.0 until 9.5.0, kedrodatasetsexperimental.pytorch.PyTorchDataset in kedro-datasets loads .pt model files with torch.load without enforcing weightsonly=True, and user-supplied loadargs are silently dropped. On PyTorch versions…
When was CVE-2026-62997 disclosed?
CVE-2026-62997 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62997 actively exploited?
CVE-2026-62997 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.5% of all scored CVEs.
What is the CVSS score of CVE-2026-62997?
CVE-2026-62997 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-62997?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62997, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62997

Explore →

Is Your Infrastructure Affected by CVE-2026-62997?

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

Start Free Scan →Browse All CVEs