Graylog session fixation vulnerability through cookie injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.7 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2024-24823: 0.41% estimated exploitation activity in the next 30 days; percentile 35.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Reauthenticating with an existing session cookie would re-use that session id, even if for different user credentials. In this case, the pre-existing session could be used to gain elevated access to an existing Graylog login session, provided the malicious user could successfully inject their session cookie into someone else's browser. The complexity of such an attack is high, because it requires presenting a spoofed login screen and injection of a session cookie into an existing browser, potentially through an XSS attack. No such attack has been discovered. Patches Graylog 5.1.11 and 5.2.4, and any versions of the 6.0 development branch contain patches to not re-use sessions under any circumstances, making this type of attack impossible. Workarounds Using short session expiration and explicit log outs of unused sessions can help limiting the attack vector. Unpatched this vulnerability exists, but is relatively hard to exploit. A proxy could be leveraged to clear the…

Published by the source

7 Feb 2024, 18:24 UTC

Last modified by the source

17 Feb 2024, 05:07 UTC

Source last checked

26 Oct 2026, 16:26 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3xf8-g8gr-g7rh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-24823

Advisory: Graylog session fixation vulnerability through cookie injection
IDs: CVE-2024-24823, GHSA-3xf8-g8gr-g7rh
Record: https://patchnext.com/advisories/cve-2024-24823 (revision 1, source checked 26 Oct 2026, 16:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.graylog2:graylog2-server 5.2.4, 5.1.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.graylog2:graylog2-server: affected >= 4.3.0, < 5.1.11; >= 5.2.0-alpha.1, < 5.2.4; fixed in 5.2.4, 5.1.11

## Suggested inspection (read-only)
- Maven org.graylog2:graylog2-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.graylog2:graylog2-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3xf8-g8gr-g7rh (GitHub-reviewed advisory GHSA-3xf8-g8gr-g7rh lists affected ranges: Maven org.graylog2:graylog2-server >=4.3.0 =5.2.0-alpha.1 <5.2.4)

Commands are suggestions: review each one before running it.