# CVE-2026-69190: Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards

> Attackers with edit permissions can escalate to owner privileges on saved searches and dashboards, allowing them to delete entities or remove original owners.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-m9c2-85gv-8xr5

## What is CVE-2026-69190?

CVE-2026-69190 is a medium-severity vulnerability in graylog2-server, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Graylog is a free and open log management platform. From 6.3.0 until 6.3.14, 7.0.9, and 7.1.4, the view update API for saved searches and dashboards permits a user with edit permission but without entity ownership to include a shareRequest that grants owner permissions to an arbitrary account. The selected account can then delete the saved search or dashboard or remove the original owner's access. Graylog Cloud was patched before the advisory was published. This issue is fixed in versions 6.3.14, 7.0.9, and 7.1.4.

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

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

6 open source packages ship an affected version, including org.graylog2:graylog2-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.graylog2:graylog2-server` | Maven | From 6.3.0 | 6.3.14 |
| `org.graylog2:graylog2-server` | Maven | From 6.3.0 | 6.3.14 |
| `org.graylog2:graylog2-server` | Maven | From 7.0.0 | 7.0.9 |
| `org.graylog2:graylog2-server` | Maven | From 7.0.0 | 7.0.9 |
| `org.graylog2:graylog2-server` | Maven | From 7.1.0 | 7.1.4 |
| `org.graylog2:graylog2-server` | Maven | From 7.1.0 | 7.1.4 |

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

Upgrade org.graylog2:graylog2-server to a fixed version for your release line: 6.3.14, 7.0.9 or 7.1.4.

## Is CVE-2026-69190 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69190 is a medium-severity vulnerability in graylog2-server, published on 21 Sep 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-69190 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.graylog2:graylog2-server (Maven): affected from 6.3.0; fixed in 6.3.14
- org.graylog2:graylog2-server (Maven): affected from 6.3.0; fixed in 6.3.14
- org.graylog2:graylog2-server (Maven): affected from 7.0.0; fixed in 7.0.9
- org.graylog2:graylog2-server (Maven): affected from 7.0.0; fixed in 7.0.9
- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4
- org.graylog2:graylog2-server (Maven): affected from 7.1.0; fixed in 7.1.4

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

## Sources

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

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