Graylog can leak other users' reports via concurrent PDF report rendering

Summary

Graylog is a free and open log management platform. The reporting functionality in Graylog allows the creation and scheduling of reports which contain dashboard widgets displaying individual log messages or metrics aggregated from fields of multiple log messages. This functionality, as included in Graylog 6.1.0 & 6.1.1, is vulnerable to information leakage triggered by multiple concurrent report rendering requests from authorized users. When multiple report renderings are requested at the same start time, the headless browser instance used to render the PDF will be reused. Depending on the timing, either a check for the browser instance "freshness" hits, resulting in an error instead of the report being returned, or one of the concurrent report rendering requests "wins" and this report is returned for all report rendering requests that do not return an error. This might lead to one user getting the report of a different user, potentially leaking indexed log messages or aggregated data that this user normally has no access to. This problem is fixed in Graylog 6.1.2. There is no known workaround besides disabling the reporting functionality.

Timeline

1. Nov 18, 2024, 8:27 PM UTCCVE published
2. Nov 19, 2024, 3:37 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Sep 23, 2025, 6:27 PM UTCRecord last updated

Affected versions

• Graylog2 graylog2-server

  From 6.1.0 · fixed in 6.1.2

• org.graylog:graylog-parentMaven

  From 6.1.0 · fixed in 6.1.2

References 1