CVE-2025-46827
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGraylog is a free and open log management platform. Prior to versions 6.0.14, 6.1.10, and 6.2.0, 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). Versions 6.0.14, 6.1.10, and 6.2.0 fix the issue. No known workarounds are available, as long as the relatively rare prerequisites are met.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored XSS vulnerability in Graylog's Event Definition Remediation Step field allows authenticated attackers with event definition creation permissions to inject malicious HTML forms. When users with alert viewing permissions view these crafted event definitions, their session cookies can be exfiltrated to an attacker-controlled endpoint via the form submission.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.0.14>= 6.1.0, < 6.1.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Graylog versionRun 'graylog-ctl version' or check the Graylog web interface under System > Nodes. Also check /etc/graylog/graylog.yml for version information if available.Affected if The installed version is less than 6.0.14, or is between 6.1.0 and 6.1.10 inclusive
-
Identify users with event definition creation permissionsIn Graylog web interface, go to Users and Teams or Roles section. Look for roles with 'Event Definition' create or write permissions.Affected if Users exist who have the ability to create or edit event definitions
-
Inspect event definitions for suspicious Remediation Step contentNavigate to Alerts > Event Definitions. For each event definition, edit it and examine the 'Remediation Steps' or similar field. Look for HTML <form> tags, <script> tags, or unexpected external URLs.Affected if Any event definition contains HTML form tags, script tags, or URLs pointing to unexpected domains in the Remediation Step field
-
Review audit and server logs for cookie exfiltrationCheck Graylog server logs and audit logs for patterns like POST requests to external domains, or searches for event definitions that may indicate unauthorized access. Look for anomalous network connections originating from Graylog servers.Affected if Logs show POST submissions from Graylog to external unknown domains, or unusual outbound connections from the Graylog server
You are affected if your Graylog version falls within the vulnerable ranges AND event definitions exist with malicious HTML content in the Remediation Step field that could exfiltrate session cookies.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.0.146.1.10
Upgrade Graylog to version 6.0.14, 6.1.10, or 6.2.0 which patches this vulnerability. No workarounds exist; the attack requires relatively rare prerequisites but should be addressed promptly.
Graylog 6.0.14, 6.1.10, or 6.2.0 (choose the appropriate version based on your current release line)
- 1. Identify the current Graylog version installed in your environment using the Graylog web interface (System > Nodes) or the API
- 2. Based on your current version, plan the upgrade path: If running < 6.0.14 on the 6.0.x line, upgrade to 6.0.14 or later; If running >= 6.1.0 and < 6.1.10 on the 6.1.x line, upgrade to 6.1.10 or later
- 3. Before upgrading, backup your Graylog configuration, database, and any custom content (event definitions, dashboards, etc.)
- 4. Stop the Graylog server and all related services
- 5. Follow the official Graylog upgrade documentation for your operating system to install the target version (6.0.14, 6.1.10, or 6.2.0)
- 6. Start the Graylog server and verify all services are running correctly
- 7. Verify the upgrade was successful by checking the Graylog version in System > Nodes
- 8. Test that Event Definitions with Remediation Steps function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46827 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data