# CVE-2026-116018: ONEARMY community-platform before 2.165.2 IDOR via notification read endpoint


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-rq5g-4m5j-8p36

## What is CVE-2026-116018?

CVE-2026-116018 is a medium-severity vulnerability in ONEARMY community-platform, published on 24 Oct 2026. 

### Official description

ONEARMY community-platform before 2.165.2 contains an insecure direct object reference vulnerability that allows authenticated users to mark other users' notifications as read via POST /api/notifications/:id/read. Attackers can iterate sequential notification IDs to suppress unread indicators of users in the same tenant, causing them to miss replies, comments and new-content notices.

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

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


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

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

## Is CVE-2026-116018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116018 is a medium-severity vulnerability in ONEARMY community-platform, published on 24 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116018 exists.

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

## Sources

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

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