CVE-2025-30373 Details
Description
Graylog is a free and open log management platform. Starting with 6.1, HTTP Inputs can be configured to check if a specified header is present and has a specified value to authenticate HTTP-based ingestion. Unfortunately, even though in cases of a missing header or a wrong value the correct HTTP response (401) is returned, the message will be ingested nonetheless. To mitigate the vulnerability, disable http-based inputs and allow only authenticated pull-based inputs. This vulnerability is fixed in 6.1.9.
An authentication bypass vulnerability has been identified in Graylog versions 6.1.0 and later. This issue arises in HTTP Inputs configured to require a specific header for authentication. Despite returning the correct HTTP response (401) when the header is missing or the value is incorrect, the messages are still ingested. This vulnerability can be mitigated by disabling HTTP-based inputs and using only authenticated pull-based inputs. The issue has been fixed in Graylog version 6.1.9.
Users can upgrade to Graylog version 6.1.9 or later to address this vulnerability. Alternatively, HTTP-based inputs can be disabled in favor of authenticated pull-based inputs.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 8, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-285 | Improper Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| graylog graylog | >= 6.1.0, < 6.1.9 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2025 | Initial Analysis | [email protected] |
| Apr 7, 2025 | New CVE Received | [email protected] |