`CVE-2023-41041` Graylog

Affected software	Graylog
Severity	3.1 Low CVSS 3.1 2 scores
Fixed in	`5.0.9`, `5.1.3`
Weakness	CWE-613
Published	30 Aug 2023
Updated	17 Jun 2026

Description

Graylog is a free and open log management platform. 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. 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. 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. This issue has been addressed in versions 5.0.9 and 5.1.3. Users are advised to upgrade.

Exploitation status

Proof of concept only

A proof of concept exists, but no reviewed exploit catalogue lists this CVE.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: poc CISA recorded that an exploit has been demonstrated. Automatable: no, technical impact: partial.
Indexed PoC none indexed
EPSS 0.48% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: Graylog2/graylog2-server bb88f3d.

Protection none
Action unverified
Review automated Upstream data
Record active

Decided by	Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding	This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix	https://github.com/Graylog2/graylog2-server/commit/bb88f3d0b2b0351669ab32c60b595ab7242a3fe3 : a commit: the change itself

Decided by

Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

Finding

This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Candidate fix

https://github.com/Graylog2/graylog2-server/commit/bb88f3d0b2b0351669ab32c60b595ab7242a3fe3 : a commit: the change itself

CVSS

3.1 LOW v3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 3.1 LOW CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N NVD Primary published

CVSS 3.1 2.6 LOW CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N security-advisories@github.com Secondary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	3.1	LOW	`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`	NVD	Primary	published
CVSS 3.1	2.6	LOW	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`	security-advisories@github.com	Secondary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package Introduced Fixed Last affected

org.graylog2:graylog2-server 1.0 5.0.9 unbounded

org.graylog2:graylog2-server 5.1.0 5.1.3 unbounded

Package	Introduced	Fixed	Last affected
`org.graylog2:graylog2-server`	1.0	`5.0.9`	unbounded
`org.graylog2:graylog2-server`	5.1.0	`5.1.3`	unbounded

Products and versions

2 products, 4 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	graylog	graylog	generic	≥ 1.0.0 and ＜ 5.0.9 · ≥ 5.1.0 and ＜ 5.1.3
osv	org.graylog2	graylog2-server	generic	≥ 1.0 and ＜ 5.0.9 · ≥ 5.1.0 and ＜ 5.1.3

Source

Vendor

Product

Scheme

Affected versions

nvd

graylog

generic

≥ 1.0.0 and ＜ 5.0.9 · ≥ 5.1.0 and ＜ 5.1.3

osv

org.graylog2

graylog2-server

generic

≥ 1.0 and ＜ 5.0.9 · ≥ 5.1.0 and ＜ 5.1.3

References

URL	Tags
https://github.com/Graylog2/graylog2-server/commit/bb88f3d0b2b0351669ab32c60b595ab7242a3fe3	commit
https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-3fqm-frhg-7c85	WEB
https://github.com/Graylog2/graylog2-server/commit/ff90f3e2aa4ae2e0bb613d3236e52c40aa154b20	WEB
https://github.com/Graylog2/graylog2-server	PACKAGE

URL

Timeline

Published	2023-08-30	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.

Published

2023-08-30

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

How VRT decided (17 of 24 rules ran)

17 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification no match A researcher's recorded decision for this specific CVE

5 manual classification no match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side no match Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven matched In scope Maven packages: org.graylog2:graylog2-server

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint matched Mitigation candidate References include candidate fix URL (commit tier): https://github.com/Graylog2/graylog2-server/commit/bb88f3d0b2b0351669ab32c60b595ab7242a3fe3

18 open-source-maven skipped The affected package being open source on Maven, so the fix can be read

19 poc-derivable skipped An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit skipped Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match no match A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc skipped Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold withheld CISA Vulnrichment records exploitation "poc" — a demonstrated exploit exists, so severity does not settle it despite no indexed PoC artifact

24 no-exploit-published decided it matched No exploit published No exploit code has been published, and an upstream fix path does exist, so the remediation half of the candidacy still holds.

Products the scope rules checked

The products this CVE's record names, and whether VRT tracks each one. The scope rules decided on these.

Vendor Product Tracked CPE Source

graylog graylog not tracked cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*

NVD ↗ · CVE.org ↗