Advisoriesby IbisGraylogGHSA-q7g5-jq6p-6wvx
Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong value
Fix: upgrade to 6.1.9 or later
Impact
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.
Patches
Workarounds
Disabling http-based inputs and allow only authenticated pull-based inputs.
Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| org.graylog2:graylog2-server Maven | >= 6.1.0, < 6.1.9 | 6.1.9 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-285
- Also known as
- CVE-2025-30373
More Graylog advisories
All Graylog
Graylog Server: System Catalog titles endpoint can be used to retrieve values of protected database fieldsCVE-2026-55425fixed in 7.1.4Graylog vulnerable to privilege escalation through API tokensCVE-2025-53106fixed in 6.2.4 +1Graylog Allows Session Takeover via Insufficient HTML SanitizationCVE-2025-46827fixed in 6.0.14 +1Graylog Allows Stored Cross-Site Scripting via Files Plugin and API BrowserGHSA-q9q2-3ppx-mwqffixed in 6.2.0Graylog session fixation vulnerability through cookie injectionCVE-2024-24823fixed in 5.1.11 +1Graylog vulnerable to instantiation of arbitrary classes triggered by API requestCVE-2024-24824fixed in 5.1.11 +1