CVE-2026-86169

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-05. a secondary CVSS source baseline 8.8; sources differ by 0.0.

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

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

Axolotl before 0.19.0 contains a remote code execution vulnerability in the multipack patch path where trust_remote_code defaults to None instead of False, causing the security guard to be bypassed. Attackers can execute arbitrary Python code by crafting a malicious Hugging Face model repository selected as base_model, which is loaded with hardcoded trust_remote_code=True during AutoModelForCausalLM.from_pretrained.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

September 5, 2026

Last Modified

September 12, 2026

Advisory Details (6)

Auto-updated Sep 5, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Axolotl through 0.18.0 Remote Code Execution via Multipack Patching | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axolotl-through-0.18.0-remote-code-execution-via-multipack-patching
generic

GitHub - axolotl-ai-cloud/axolotl: Go ahead and axolotl questions · GitHub

https://github.com/axolotl-ai-cloud/axolotl
generic

axolotl/src/axolotl/monkeypatch/multipack.py at v0.18.0 · axolotl-ai-cloud/axolotl · GitHub

https://github.com/axolotl-ai-cloud/axolotl/blob/v0.18.0/src/axolotl/monkeypatch/multipack.py#L86-L96
generic

axolotl/src/axolotl/loaders/patch_manager.py at v0.18.0 · axolotl-ai-cloud/axolotl · GitHub

https://github.com/axolotl-ai-cloud/axolotl/blob/v0.18.0/src/axolotl/loaders/patch_manager.py#L794-L806
github_commit

commit b62d60b101ee (axolotl-ai-cloud/axolotl)

Fix landed in axolotl-ai-cloud/axolotl commit b62d60b101ee — awaiting tagged release

https://github.com/axolotl-ai-cloud/axolotl/commit/b62d60b101eea7f32532ee3c0b17c2f2430a9262
github_pr

fix: handle trust_remote_code when packing properly

Fix merged in axolotl-ai-cloud/axolotl PR #3858 on 2026-07-24 — awaiting tagged release

https://github.com/axolotl-ai-cloud/axolotl/pull/3858

Vendor Advisories for CVE-2026-86169(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 60× 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-19 14:36 UTCGHSA enrichment
  2. 2026-09-19 02:29 UTCEG score recompute
  3. 2026-09-19 02:29 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 14:23 UTCGHSA enrichment
  6. 2026-09-18 02:18 UTCEG score recompute
  7. 2026-09-18 02:18 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 14:13 UTCGHSA enrichment
  10. 2026-09-17 02:02 UTCEG score recompute
  11. 2026-09-17 02:02 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 13:56 UTCEG score recompute
  14. 2026-09-16 13:56 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 01:06 UTCGHSA enrichment
  17. 2026-09-15 13:00 UTCEG score recompute
  18. 2026-09-15 13:00 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 00:54 UTCGHSA enrichment
  22. 2026-09-14 12:48 UTCGHSA enrichment
  23. 2026-09-14 00:42 UTCEG score recompute
  24. 2026-09-14 00:42 UTCGHSA enrichment
  25. 2026-09-13 12:37 UTCGHSA enrichment
Show 35 more
  1. 2026-09-13 00:30 UTCEG score recompute
  2. 2026-09-13 00:30 UTCGHSA enrichment
  3. 2026-09-12 12:24 UTCGHSA enrichment
  4. 2026-09-12 00:18 UTCEG score recompute
  5. 2026-09-12 00:18 UTCGHSA enrichment
  6. 2026-09-11 23:29 UTCEG score recompute
  7. 2026-09-11 23:29 UTCGHSA enrichment
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 11:56 UTCEG score recompute
  11. 2026-09-11 11:56 UTCGHSA enrichment
  12. 2026-09-10 23:50 UTCGHSA enrichment
  13. 2026-09-10 11:25 UTCEG score recompute
  14. 2026-09-10 11:25 UTCGHSA enrichment
  15. 2026-09-09 23:20 UTCGHSA enrichment
  16. 2026-09-09 08:00 UTCEG score recompute
  17. 2026-09-09 08:00 UTCGHSA enrichment
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 19:55 UTCEG score recompute
  20. 2026-09-08 19:55 UTCGHSA enrichment
  21. 2026-09-08 16:16 UTCGHSA enrichment
  22. 2026-09-08 02:02 UTCEG score recompute
  23. 2026-09-08 02:02 UTCGHSA enrichment
  24. 2026-09-07 13:56 UTCEG score recompute
  25. 2026-09-07 13:56 UTCGHSA enrichment
  26. 2026-09-07 11:49 UTCGHSA enrichment
  27. 2026-09-06 23:41 UTCEG score recompute
  28. 2026-09-06 23:41 UTCGHSA enrichment
  29. 2026-09-06 13:48 UTCEPSS rescore
  30. 2026-09-06 11:34 UTCGHSA enrichment
  31. 2026-09-05 23:29 UTCEG score recompute
  32. 2026-09-05 23:29 UTCGHSA enrichment
  33. 2026-09-05 11:22 UTCEG score recompute
  34. 2026-09-05 11:04 UTCEG score recompute
  35. 2026-09-05 11:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86169?
CVE-2026-86169 is a high vulnerability published on September 5, 2026. Axolotl before 0.19.0 contains a remote code execution vulnerability in the multipack patch path where trustremotecode defaults to None instead of False, causing the security guard to be bypassed. Attackers can execute arbitrary Python code by crafting a malicious Hugging Face model repository…
When was CVE-2026-86169 disclosed?
CVE-2026-86169 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86169 actively exploited?
CVE-2026-86169 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 58.5% of all scored CVEs.
What is the CVSS score of CVE-2026-86169?
CVE-2026-86169 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-86169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86169, 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-86169

Explore →

Is Your Infrastructure Affected by CVE-2026-86169?

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

Start Free Scan →Browse All CVEs