CVE-2026-94212

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). 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 — 4 sources updated this week
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper verification of cryptographic signature vulnerability in Apache APISIX.

Any unauthenticated attacker could impersonate any user on every route protected by the saml-auth plugin under default configuration. This issue affects Apache APISIX: from 3.17.0 through 3.18.0.

Users are recommended to upgrade to version 3.19.0, which fixes the issue.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 1, 2026

Last Modified

October 1, 2026

Advisory Details (1)

Auto-updated Oct 1, 2026
Fix named in the CVE record.

Vendor Advisories for CVE-2026-94212(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 17× in last 7d / 17× 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-10-03 18:58 UTCEG score recompute
  2. 2026-10-03 18:58 UTCGHSA enrichment
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-02 17:57 UTCEPSS rescore
  5. 2026-10-02 17:10 UTCGHSA enrichment
  6. 2026-10-01 15:23 UTCEG score recompute
  7. 2026-10-01 15:23 UTCGHSA enrichment
  8. 2026-10-01 15:01 UTCEG score recompute
  9. 2026-10-01 15:01 UTCGHSA enrichment
  10. 2026-10-01 14:20 UTCEG score recompute
  11. 2026-10-01 14:20 UTCGHSA enrichment
  12. 2026-10-01 13:31 UTCEG score recompute
  13. 2026-10-01 13:31 UTCGHSA enrichment
  14. 2026-10-01 12:57 UTCGHSA enrichment
  15. 2026-10-01 12:28 UTCEG score recompute
  16. 2026-10-01 11:21 UTCEG score recompute
  17. 2026-10-01 11:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-94212?
CVE-2026-94212 is a medium vulnerability published on October 1, 2026. Improper verification of cryptographic signature vulnerability in Apache APISIX. Any unauthenticated attacker could impersonate any user on every route protected by the saml-auth plugin under default configuration. This issue affects Apache APISIX: from 3.17.0 through 3.18.0. Users are recommended…
When was CVE-2026-94212 disclosed?
CVE-2026-94212 was first published on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94212 actively exploited?
CVE-2026-94212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94212?
CVE-2026-94212 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-94212?
A fix for CVE-2026-94212 is available — its CVE record says: "Users are recommended to upgrade to version 3.19.0, which fixes the issue." The vendor advisories EchelonGraph has for CVE-2026-94212 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-94212?

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