# CVE-2026-109359: Contrast 1.8.0 before 1.24.1 Mesh CA Key Cross-Manifest Exposure via Peer Recovery

> Attackers can expose the Mesh CA key or issue trusted certificates to withdrawn workloads by exploiting improper verification in peer recovery.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-mr8p-7h3w-x7jp, GHSA-rxcv-p3px-m3c3

## What is CVE-2026-109359?

CVE-2026-109359 is a high-severity vulnerability in edgelesssys contrast, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Contrast 1.8.0 before 1.24.1 contains an improper verification vulnerability in Coordinator peer recovery that fails to confirm the serving peer uses the same manifest generation. Attackers with write access to manifest history can replay a superseded history head so withdrawn workloads obtain trusted mesh certificates, or with the secret seed disclose the Mesh CA key.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-109359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109359 is a high-severity vulnerability in edgelesssys contrast, published on 12 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109359 in the wild and no public exploit code.

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

## Sources

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

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