# CVE-2026-47657: HumHub Missing Authorization on Remove All Space Members Action

> An authenticated attacker can remove all members from any space in HumHub due to missing authorization checks, requiring an upgrade to fix.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-hj67-5q6h-j7c2

## What is CVE-2026-47657?

CVE-2026-47657 is a high-severity missing authorization vulnerability in humhub, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HumHub is an Open Source Enterprise Social Network. In versions 1.13.0 through 1.18.2, a missing authorization check in the Space member management controller allowed any authenticated user to trigger the removal of all members from any Space, regardless of their own role or membership in that Space. Versions 1.13.0 through 1.18.2 are affected. The vulnerability has been patched in version 1.18.3, and all users are encouraged to upgrade to this version or later immediately. No known workaround is available.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-47657 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47657 is a high-severity missing authorization vulnerability in humhub, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47657 in the wild and no public exploit code.

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

## Sources

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

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