# CVE-2026-11369: IDOR in Comment API Allows Cross-Process Comment Read and Write

> Authenticated users can read and write comments on any process across all business units by manipulating object IDs in the Comment API.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-8rq4-278f-v3vj

## What is CVE-2026-11369?

CVE-2026-11369 is a high-severity missing authorization vulnerability in linqi, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Comment API (GET /api/Comment and POST /api/Comment) in the affected application fails to perform authorization checks to verify that the requesting user has access to the object identified by the relatedObjectId. This Insecure Direct Object Reference (IDOR) vulnerability allows any authenticated user to read and write comments on any process across all business units by supplying an arbitrary object GUID.

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

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


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

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

## Is CVE-2026-11369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11369 is a high-severity missing authorization vulnerability in linqi, published on 5 Jun 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-11369 in the wild and no public exploit code.

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

## Sources

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

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