Summary
Graylog concurrent PDF report rendering can leak other users' reports
Workarounds
There is no known workaround besides disabling the reporting functionality.
References
Impact
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This problem is fixed in Graylog 6.1.2.
Frequently Asked Questions
- What is CVE-2024-52506? CVE-2024-52506 is a high-severity security vulnerability in org.graylog:graylog-parent (maven), affecting versions >= 6.1.0, < 6.1.2. It is fixed in 6.1.2.
- Which versions of org.graylog:graylog-parent are affected by CVE-2024-52506? org.graylog:graylog-parent (maven) versions >= 6.1.0, < 6.1.2 is affected.
- Is there a fix for CVE-2024-52506? Yes. CVE-2024-52506 is fixed in 6.1.2. Upgrade to this version or later.
- Is CVE-2024-52506 exploitable, and should I be worried? Whether CVE-2024-52506 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2024-52506 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2024-52506? Upgrade
org.graylog:graylog-parentto 6.1.2 or later.