# CVE-2026-115804: Consul vulnerable to an authorization bypass in health check registration


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-9vq3-c4rf-pm8v, UBUNTU-CVE-2026-115804

## What is CVE-2026-115804?

CVE-2026-115804 is a medium-severity vulnerability in HashiCorp Consul, published on 26 Oct 2026. 

### Official description

HashiCorp Consul and Consul Enterprise are vulnerable to an authorization bypass in health check registration that may allow an authenticated user to modify health checks belonging to another service on the same node. This vulnerability (CVE-2026-115804) is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-115804 being exploited?

There is no known exploitation of CVE-2026-115804 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115804 is a medium-severity vulnerability in HashiCorp Consul, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115804 in the wild and no public exploit code.

Affected product: HashiCorp Consul. 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-115804/ (Markdown: https://insights.sbomify.com/CVE-2026-115804/index.md)
```

## Sources

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

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