# CVE-2026-22679: Weaver E-cology 10.0 Unauthenticated RCE via dubboApi Debug Endpoint

> Unauthenticated attackers can execute arbitrary commands via exposed debug endpoints in Weaver E-cology, requiring immediate patching.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 7 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-vg4v-xjcr-x7p5

## What is CVE-2026-22679?

CVE-2026-22679 is a critical code injection vulnerability in Weaver Network Co., Ltd. E-cology, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Weaver (Fanwei) E-cology 10.0 versions prior to 20260312 contain an unauthenticated remote code execution vulnerability in the /papi/esearch/data/devops/dubboApi/debug/method endpoint that allows attackers to execute arbitrary commands by invoking exposed debug functionality. Attackers can craft POST requests with attacker-controlled interfaceName and methodName parameters to reach command-execution helpers and achieve arbitrary command execution on the system. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-31 (UTC).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Weaver E-Cology.

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

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

## Is CVE-2026-22679 being exploited?

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

Public exploit code:

- Critical RCE vulnerability (CVSS 9.3) in Weaver E-cology platform versions prior to build 20260312. Unauthenticated remote code execution via exposed debug endpoint at /papi/esearch/data/devops/dubboApi/debug/method. Comprehensive analysis, proof-of-concept, and detection guidance included. (github_poc): https://github.com/keraattin/CVE-2026-22679

## Other vulnerabilities in Weaver Network Co., Ltd. E-cology

- [CVE-2024-48069](https://insights.sbomify.com/CVE-2024-48069/): Race condition in n/a (critical 9.8)
- [CVE-2024-48070](https://insights.sbomify.com/CVE-2024-48070/): Code injection in n/a (critical 9.8)
- [CVE-2024-48072](https://insights.sbomify.com/CVE-2024-48072/): SQL injection in n/a (critical 9.8)
- [CVE-2023-51892](https://insights.sbomify.com/CVE-2023-51892/): Code injection in n/a (critical 9.8)
- [CVE-2025-34038](https://insights.sbomify.com/CVE-2025-34038/): Weaver E-cology SQL Injection (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22679 is a critical code injection vulnerability in Weaver Network Co., Ltd. E-cology, published on 7 Apr 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-22679 exists.

Affected product: Weaver Network Co., Ltd. E-cology. 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-22679/ (Markdown: https://insights.sbomify.com/CVE-2026-22679/index.md)
```

## Sources

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

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