# CVE-2026-91997: evolution-api through 2.3.7 Prometheus Metrics IP Allowlist Bypass

> Attackers can bypass IP whitelist restrictions to access sensitive metrics, disclosing server details and configuration information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-755x-c9g7-3hr7

## What is CVE-2026-91997?

CVE-2026-91997 is a medium-severity authentication bypass vulnerability in evolution-foundation evolution-api, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-697 (Incorrect Comparison)

## Which versions are affected by CVE-2026-91997?


## How do I fix CVE-2026-91997?

No fix has been published for CVE-2026-91997 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91997 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91997 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91997 and fix it if it is affected.

What it is: CVE-2026-91997 is a medium-severity authentication bypass vulnerability in evolution-foundation evolution-api, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91997 exists.

Affected product: evolution-foundation evolution-api. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91997/ (Markdown: https://insights.sbomify.com/CVE-2026-91997/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91997
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91997
- OSV: https://osv.dev/vulnerability/CVE-2026-91997

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91997/
Summaries are generated and may contain mistakes; the official description above is the record.