Advisoriesby IbisGraylogGHSA-76vf-mpmx-777j
Graylog Allows Session Takeover via Insufficient HTML Sanitization
Fix: upgrade to 6.0.14 or later (2 fixed versions below)
Impact
It is possible to obtain user session cookies by submitting an HTML form as part of an Event Definition Remediation Step field.
For this attack to succeed, the attacker needs a user account with permissions to create event definitions, while the user must have permissions to view alerts. Additionally, an active Input must be present on the Graylog server that is capable of receiving form data (e.g. a HTTP input, TCP raw or syslog etc).
Patches
Workarounds
None, as long as the relatively rare prerequisites are met.
Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| org.graylog2:graylog2-server Maven | < 6.0.14 | 6.0.14 |
| >= 6.1.0, < 6.1.10 | 6.1.10 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-79
- Also known as
- CVE-2025-46827
More Graylog advisories
All Graylog
Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fieldsCVE-2026-55425fixed in 7.1.4Graylog vulnerable to privilege escalation through API tokensCVE-2025-53106fixed in 6.2.4 +1Graylog Allows Stored Cross-Site Scripting via Files Plugin and API BrowserGHSA-q9q2-3ppx-mwqffixed in 6.2.0Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong valueCVE-2025-30373fixed in 6.1.9Graylog session fixation vulnerability through cookie injectionCVE-2024-24823fixed in 5.1.11 +1Graylog vulnerable to instantiation of arbitrary classes triggered by API requestCVE-2024-24824fixed in 5.1.11 +1