ONTAP versions 9.16.1 and higher with WebAuthn multi-factor authentication (MFA) configured are susceptible to a vulnerability related to the Relying Party ID which when successfully exploited could allow an attacker with valid credentials to bypass MFA.
CVE-2026-22049
HIGHPre-NVD 8.78.7Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.7 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).
Triggered by: NVD CVSS baseline
Sources: secondary
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.7Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(low)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity87% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 39.9%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026No patch confirmed yet.
Vendor Advisories for CVE-2026-22049(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 6× in last 7d / 6× 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-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:06 UTCEG score recompute
- 2026-07-22 20:53 UTCEG score recompute
- 2026-07-22 19:02 UTCEG score recompute
- 2026-07-22 19:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-288
- CVE-2019-25763EG 9.8CRITICAL
- CVE-2022-25369EG 9.8EPSS 99%CRITICAL
- CVE-2020-36724EG 9.8CRITICAL
- CVE-2020-36713EG 9.8CRITICAL
- CVE-2022-46732EG 9.8CRITICAL
- CVE-2022-27510EG 9.8CRITICAL
- CVE-2022-26870NVD 7.0EG 9.8HIGH
- CVE-2022-23767NVD 8.8EG 9.8HIGH
- CVE-2022-34372EG 9.8CRITICAL
- CVE-2022-35869EG 9.8EPSS 99%CRITICAL
Frequently asked(5)
What is CVE-2026-22049?
CVE-2026-22049 is a high vulnerability published on July 22, 2026. ONTAP versions 9.16.1 and higher with WebAuthn multi-factor authentication (MFA) configured are susceptible to a vulnerability related to the Relying Party ID which when successfully exploited could allow an attacker with valid credentials to bypass MFA.
When was CVE-2026-22049 disclosed?
CVE-2026-22049 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22049 actively exploited?
CVE-2026-22049 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22049?
CVE-2026-22049 has a CVSS v3 base score of 8.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-22049?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22049, 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-22049
Is Your Infrastructure Affected by CVE-2026-22049?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.