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.
CVE-2024-24824
“—” beside the score: it is equal to NVD's CVSS score.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2024-02-07. NVD baseline CVSS 8.8; sources differ by 0.0.
Also known asEUVD-2024-0682 (ENISA EUVD) · GHSA-p6gg-5hf4-4rgj (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHmedium confidence
- EG Risk
- 71EG Risk 71/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 35%
- EPSS %ILE
- 98th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 35% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
February 7, 2024
Last Modified
November 21, 2024
Advisory Details (4)
Auto-updated Jul 27, 2026Instantiation of arbitrary classes triggered by API request · Advisory · Graylog2/graylog2-server · GitHub
https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-p6gg-5hf4-4rgjcommit 7f8ef7fa8edf (Graylog2/graylog2-server)
Fix landed in Graylog2/graylog2-server commit 7f8ef7fa8edf — awaiting tagged release
https://github.com/Graylog2/graylog2-server/commit/7f8ef7fa8edf493106d5ef6f777d4da02c5194d9commit 75ef2b8d60e7 (Graylog2/graylog2-server)
Fix landed in Graylog2/graylog2-server commit 75ef2b8d60e7 — awaiting tagged release
https://github.com/Graylog2/graylog2-server/commit/75ef2b8d60e7d67f859b79fe712c8ae7b2e861d8graylog2-server/graylog2-server/src/main/java/org/graylog2/rest/resources/system/ClusterConfigResource.java at e458db8bf4f789d4d19f1b37f0263f910c8d036c · Graylog2/graylog2-server · GitHub
https://github.com/Graylog2/graylog2-server/blob/e458db8bf4f789d4d19f1b37f0263f910c8d036c/graylog2-server/src/main/java/org/graylog2/rest/resources/system/ClusterConfigResource.java#L208-L214Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| maven | org.graylog2:graylog2-server @ 5.1.11 (fixes >= 2.0.0, < 5.1.11) | — | ghsa |
| maven | org.graylog2:graylog2-server @ 5.2.4 (fixes >= 5.2.0-alpha.1, < 5.2.4) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.graylog2:graylog2-server | 5.2.0 ... 5.2.3 (10 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 36× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 96 of 181 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:40 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-11-01 08:15 UTCGHSA enrichmentGHSA-p6gg-5hf4-4rgj · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-01 08:15 UTCEG score recompute
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-30 16:31 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-29 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-27 19:52 UTCEG score recompute
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-25 17:17 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-20 20:26 UTCEG score recompute
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-18 07:24 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 35% · 98th percentile
Show 71 moreShow fewer
- 2026-10-12 18:01 UTCEG score recompute
- 2026-10-11 21:25 UTCEG score recompute
- 2026-10-11 16:19 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-09 22:55 UTCOSV refresh
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-08 17:07 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-30 16:58 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-20 07:13 UTCOSV refresh
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-13 16:45 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-04 05:05 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-01 13:52 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-09-01 10:29 UTCOSV refresh
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 35% · 98th percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-15 10:07 UTCOSV refresh
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-04 15:08 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-04 10:36 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-30 21:51 UTCOSV refresh
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-30 01:29 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-28 15:34 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-26 14:53 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-24 14:16 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-23 14:17 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-23 02:34 UTCEG score recompute
- 2026-07-22 23:21 UTCEG score recompute
- 2026-07-22 14:07 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-20 17:06 UTCEPSS rescoreEPSS 34% · 98th percentile
- 2026-07-19 14:30 UTCEPSS rescoreEPSS 34% · 98th percentile
Related CVEs(same product + same CWE)
Same product
10 shownMaven:org.graylog2:graylog2-server
Frequently asked(5)
What is CVE-2024-24824?
When was the CVE record for CVE-2024-24824 published?
Is CVE-2024-24824 actively exploited?
What is the CVSS score of CVE-2024-24824?
How do I remediate CVE-2024-24824?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-24824
Is Your Infrastructure Affected by CVE-2024-24824?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.