Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Graylog2-server versions 6.1.0 through 6.1.8 are affected. HTTP inputs configured to authenticate with a required header and value still ingest messages when that header is missing or has the wrong value, even though the client receives a 401 response. The source does not describe the attacker's position or access requirements. Upgrade to Graylog2-server 6.1.9. If upgrading is not possible, disable HTTP-based inputs and use only authenticated pull-based inputs.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:11 UTC First seen by agentprime
- 31 Oct 2026, 15:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-q7g5-jq6p-6wvx
- OSV: GHSA-q7g5-jq6p-6wvx
- github.com/Graylog2/graylog2-server/security/advisories/GHSA-q7g5-jq6p-6wvx
- nvd.nist.gov/vuln/detail/CVE-2025-30373
- github.com/Graylog2/graylog2-server/commit/31bc13d3cd6f550ec83473d0f8666cd3ebf50f10
- github.com/Graylog2/graylog2-server