Read the docs
TI-2024-16341 Aliases CVE-2024-24824GHSA-p6gg-5hf4-4rgj

graylog2-server vulnerable to instantiation of arbitrary classes triggered by API request

Priority HIGH 77CWE-284Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-284.

Summary

Graylog is a free and open log management platform. Starting in version 2.0.0 and prior to versions 5.1.11 and 5.2.4, arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint. Graylog's cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader. If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated. This will execute arbitrary code that is run during class instantiation. In the specific use case of `java.io.File`, the behavior of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request. Versions 5.1.11 and 5.2.4 contain a fix for this issue.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.34739 98th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed graylog2-server (Graylog2): 5.1.11, 5.2.4org.graylog2:graylog2-server (Maven): 5.1.11, 5.2.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Graylog2graylog2-server2.0.0 to before 5.1.11; 5.2.0 to before 5.2.45.1.11, 5.2.4Patch availableCNA
—org.graylog2:graylog2-server (Maven)2.0.0 to before 5.1.115.1.11Patch availableGHSA-p6gg-5hf4-4rgj
—org.graylog2:graylog2-server (Maven)5.2.0-alpha.1 to before 5.2.45.2.4Patch availableGHSA-p6gg-5hf4-4rgj
  • graylog2-server VendorGraylog2 Affected 2.0.0 to before 5.1.11; 5.2.0 to before 5.2.4 Fixed in 5.1.11, 5.2.4 Patch available CNA
  • org.graylog2:graylog2-server (Maven) Vendor— Affected 2.0.0 to before 5.1.11 Fixed in 5.1.11 Patch available GHSA-p6gg-5hf4-4rgj
  • org.graylog2:graylog2-server (Maven) Vendor— Affected 5.2.0-alpha.1 to before 5.2.4 Fixed in 5.2.4 Patch available GHSA-p6gg-5hf4-4rgj

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:*2.0.0 to before 5.1.11; 5.2.0 to before 5.2.4VulnerableGraylog2
  • cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:* Versions 2.0.0 to before 5.1.11; 5.2.0 to before 5.2.4 Vulnerable ·Graylog2

Remediation

  • Fix · CNA graylog2-server (Graylog2) Fixed in 5.1.11, 5.2.4
  • Fix · GHSA-p6gg-5hf4-4rgj org.graylog2:graylog2-server (Maven) Fixed in 5.1.11 Advisory →
  • Fix · GHSA-p6gg-5hf4-4rgj org.graylog2:graylog2-server (Maven) Fixed in 5.2.4 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-24824
  2. 2026-10-03 Alias added: GHSA-p6gg-5hf4-4rgj

References

Exploit 1

Patch 2

Advisory 1

Other 2

  • TI-2023-21671 Insecure source port usage for DNS queries in Graylog CVSS 3.1MEDIUM 5.3
  • TI-2026-01133 Incorrect management of session invalidation vulnerability in Graylog Web Interface CVSS 4.0CRITICAL 9.3
  • TI-2023-21667 User session is still usable after logout in graylog2-server CVSS 3.1LOW 3.1
  • TI-2021-15624 A Session ID leak in the audit log in Graylog before 4.1.2 allows attackers to escalate… CVSS 3.1CRITICAL 9.8
  • TI-2021-15623 A Session ID leak in the DEBUG log file in Graylog before 4.1.2 allows attackers to… CVSS 3.1CRITICAL 9.8
  • TI-2025-33099 Graylog vulnerable to privilege escalation through API tokens CVSS 4.0HIGH 8.8
See all 21 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences