CVE-2026-69190 is a medium-severity (CVSS 6.3) CWE-639 vulnerability in org.graylog2:graylog2-server. A fix is available for org.graylog2:graylog2-server — see the affected versions and patch details below.
Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-69190.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-69190 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.graylog2:graylog2-server☕org.graylog2:graylog2-server☕org.graylog2:graylog2-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A vulnerability was found in Graylog's API endpoint for updating saved searches and dashboards. A user with edit permissions on a dashboard or saved search could grant owner permissions to an arbitrary account, which could then be used to delete the respective saved search or dashboard or to remove the original owner's access.
Patches
This issue has been patched in the following Graylog versions: 6.3.14, 7.0.9, 7.1.4. Affected users should upgrade to one of these versions or above to remediate the vulnerability.
Graylog Cloud has already been patched.
Workaround
There is no known workaround. Upgrading to a patched version is recommended.
Credits
Thanks to Jan Kahmen, turingpoint for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.graylog2:graylog2-server | ≥ 6.3.0&&< 6.3.14 | 6.3.14org.graylog2:graylog2-server:6.3.14 |
| ☕Maven | org.graylog2:graylog2-server | ≥ 7.0.0&&< 7.0.9 | 7.0.9org.graylog2:graylog2-server:7.0.9 |
| ☕Maven | org.graylog2:graylog2-server | ≥ 7.1.0&&< 7.1.4 | 7.1.4org.graylog2:graylog2-server:7.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.graylog2:graylog2-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.graylog2:graylog2-server to 6.3.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-69190 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-69190 in your dependencies?
Find it across Maven, including transitive dependencies.