In ONNX before 1.21.0, the 'save_external_data' function builds the external-data file path from the model's external_data location field and opens it for writing without 'O_NOFOLLOW/O_EXCL', after a non-atomic 'os.path.isfile()' check. A local attacker with write access to the directory where a victim serializes external data can deterministically pre-plant a symlink that is being followed, causing the victim's write to append to any file the victim can write, e.g. ~/.ssh/authorized_keys, cron files, or application configs. Fixed in 1.21.0.
CVE-2026-49114
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(low)
- EG Risk
- 48(Track)EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 21, 2026
Last Modified
August 21, 2026
Advisory Details (2)
Auto-updated Aug 21, 2026TOCTOU arbitrary file read/write in save_external_dat · Advisory · onnx/onnx · GitHub
https://github.com/onnx/onnx/security/advisories/GHSA-q56x-g2fj-4rj6Vendor Advisories for CVE-2026-49114(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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.
- 2026-08-21 17:21 UTCEG score recompute
- 2026-08-21 16:51 UTCEG score recompute
- 2026-08-21 16:20 UTCEG score recompute
- 2026-08-21 16:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-59
Frequently asked(4)
What is CVE-2026-49114?
When was CVE-2026-49114 disclosed?
What is the CVSS score of CVE-2026-49114?
How do I remediate CVE-2026-49114?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-49114
Is Your Infrastructure Affected by CVE-2026-49114?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.