evolution-api through 2.3.7 contains an incorrect array comparison in the metricsIPWhitelist middleware that always evaluates to false, allowing unauthenticated access to the /metrics endpoint. Attackers can bypass IP whitelist restrictions to access sensitive metrics disclosing server version, database client name, configured server URL, and WhatsApp instance details.
CVE-2026-91997
Score 5.3 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 55(Attend)EG Risk 55/100SSVC: Attend
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 computedSeverity53% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 15, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026evolution-api through 2.3.7 Prometheus Metrics IP Allowlist Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/evolution-api-through-2.3.7-prometheus-metrics-ip-allowlist-bypassGitHub - evolution-foundation/evolution-api: Evolution API is an open-source WhatsApp integration API · GitHub
https://github.com/evolution-foundation/evolution-apievolution-api/src/api/routes/index.router.ts at 2.3.7 · evolution-foundation/evolution-api · GitHub
https://github.com/evolution-foundation/evolution-api/blob/2.3.7/src/api/routes/index.router.ts#L49-L65oss/evolution-api.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/evolution-api.mdVendor Advisories for CVE-2026-91997(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 13× in last 7d / 13× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:57 UTCEG score recompute
- 2026-09-18 16:57 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 15:30 UTCEG score recompute
- 2026-09-17 15:30 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 13:57 UTCEG score recompute
- 2026-09-16 13:57 UTCGHSA enrichment
- 2026-09-15 12:30 UTCEG score recompute
- 2026-09-15 11:58 UTCEG score recompute
- 2026-09-15 11:43 UTCEG score recompute
- 2026-09-15 11:42 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-91997?
When was CVE-2026-91997 disclosed?
Is CVE-2026-91997 actively exploited?
What is the CVSS score of CVE-2026-91997?
How do I remediate CVE-2026-91997?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91997
Is Your Infrastructure Affected by CVE-2026-91997?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.