CVE-2026-43637
Tar‑slip path traversal in Cornac allowing archive extraction to write arbitrary files.
Is CVE-2026-43637 being exploited?
Not confirmed. CVE-2026-43637 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.66% probability of exploitation in the next 30 days.
How severe is CVE-2026-43637?
CVE-2026-43637 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-43637?
Yes. A fix has been recorded for CVE-2026-43637. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43637 affect?
CVE-2026-43637 affects Cornac < 2.6.0, Python environments using Cornac dataset loaders, ML pipelines that auto-download and extract datasets. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43637?
Upgrade to Cornac 2.6.0+ or disable/validate automatic archive extraction.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted TARs during automatic dataset extraction can write/overwrite arbitrary files, enabling code execution or system compromise under the process account.
Immediate action required
- affected< 2.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.