LowGHSA-3fqm-frhg-7c85CVE-2023-41041

Graylog user session is still usable after logout

Published 6 Jul 2023 · Updated 10 Sept 2026

Is your project on an affected org.graylog2:graylog2-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.0 <5.0.9
Fixed in
5.0.9
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=5.0.9 -DforceVersion=true
Affected
>=5.1.0 <5.1.3
Fixed in
5.1.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=5.1.3 -DforceVersion=true

Details

Summary

In a multi-node Graylog cluster, after a user has explicitly logged out, a user session may still be used for API requests until it has reached its original expiry time.

Details

Each node maintains an in-memory cache of user sessions. Upon a cache-miss, the session is loaded from the database. After that, the node operates solely on the cached session. Modifications to sessions will update the cached version as well as the session persisted in the database. However, each node maintains their isolated version of the session.

When the user logs out, the session is removed from the node-local cache and deleted from the database. The other nodes will however still use the cached session.

These nodes will only fail to accept the session id if they intent to update the session in the database. They will then notice that the session is gone. This is true for most API requests originating from user interaction with the Graylog UI because these will lead to an update of the session's "last access" timestamp.

If the session update is however prevented by setting the X-Graylog-No-Session-Extension:true header in the request, the node will consider the (cached) session valid until the session is expired according to its timeout setting.

PoC

In a 2-node setup, with both nodes behind a load balancer:

1. Log in 1. Extract the session ID from the cookie 1. Log out and close the browser 1. Perform the following API request repeatedly with curl (with <session-id> replaced with the session id from step 2 and <lb-host> replaced with the hostname of your load balancer):

    curl -I -H X-Graylog-No-Session-Extension:true https://<session-id>:session@<lb-host>/api/system/cluster/nodes

1. Notice that the request is sometimes rejected, but sometimes succeeds

Impact

No session identifiers are leaked.

After a user has logged out, the UI shows the login screen again, which gives the user the impression that their session is not valid anymore. However, if the session becomes compromised later, it can still be used to perform API requests against the Graylog cluster. The time frame for this is limited to the configured session lifetime, starting from the time when the user logged out.

Is GHSA-3fqm-frhg-7c85 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.graylog2:graylog2-server, and gives you the command that fixes it.

More advisories for org.graylog2:graylog2-server

  • MediumCVE-2026-69190Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards · 22 Sept 2026
  • MediumCVE-2026-55867Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens · 28 Aug 2026
  • HighCVE-2026-55841Fortigate syslog message parser can be exploited to modify or delete fields from the original message · 28 Aug 2026
  • MediumCVE-2026-55425Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fields · 28 Aug 2026
  • HighCVE-2025-53106Graylog vulnerable to privilege escalation through API tokens · 30 Jun 2025
  • HighCVE-2025-46827Graylog Allows Session Takeover via Insufficient HTML Sanitization · 7 May 2025
All 16 advisories for org.graylog2:graylog2-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.