CVE-2025-46827

Workarounds

None, as long as the relatively rare prerequisites are met.

Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd

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).

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-46827 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.0.14, 6.1.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-46827? CVE-2025-46827 is a high-severity cross-site scripting (XSS) vulnerability in org.graylog2:graylog2-server (maven), affecting versions <= 6.0.13. It is fixed in 6.0.14, 6.1.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-46827? CVE-2025-46827 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.graylog2:graylog2-server are affected by CVE-2025-46827? org.graylog2:graylog2-server (maven) versions <= 6.0.13 is affected.
4. Is there a fix for CVE-2025-46827? Yes. CVE-2025-46827 is fixed in 6.0.14, 6.1.10. Upgrade to this version or later.
5. Is CVE-2025-46827 exploitable, and should I be worried? Whether CVE-2025-46827 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-46827 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-46827?
   • Upgrade org.graylog2:graylog2-server to 6.0.14 or later
   • Upgrade org.graylog2:graylog2-server to 6.1.10 or later