How severe is GHSA-q7g5-jq6p-6wvx?

GHSA-q7g5-jq6p-6wvx has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q7g5-jq6p-6wvx?

GHSA-q7g5-jq6p-6wvx affects the following packages: org.graylog2:graylog2-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-q7g5-jq6p-6wvx?

Update org.graylog2:graylog2-server to 6.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7g5-jq6p-6wvx is resolved across your whole dependency graph.

How do I detect GHSA-q7g5-jq6p-6wvx in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.graylog2:graylog2-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q7g5-jq6p-6wvx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-q7g5-jq6p-6wvx actively exploited in the wild?

No public exploit code has been indexed for GHSA-q7g5-jq6p-6wvx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q7g5-jq6p-6wvx?

GHSA-q7g5-jq6p-6wvx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q7g5-jq6p-6wvx?

GHSA-q7g5-jq6p-6wvx is classified as CWE-285 (CWE-285). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q7g5-jq6p-6wvx published, and has it been updated?

GHSA-q7g5-jq6p-6wvx was published on April 7, 2025 and was last updated on May 7, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong valueGHSA-q7g5-jq6p-6wvx

MEDIUMFix: Graylog2/graylog2-server@31bc13d

GHSA-q7g5-jq6p-6wvx is a medium-severity (CVSS 6.5) CWE-285 vulnerability in org.graylog2:graylog2-server. A fix is available for org.graylog2:graylog2-server — see the affected versions and patch details below.

Also known asCVE-2025-30373

Published

Apr 7, 2025

Updated

May 7, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q7g5-jq6p-6wvx.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.graylog2:graylog2-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.graylog2:graylog2-server`	≥ 6.1.0&&< 6.1.9	6.1.9`org.graylog2:graylog2-server:6.1.9`

Affected Products

1 product · 1 configurations

Application

grayloggraylog

≥ 6.1.0 && < 6.1.9

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.graylog2:graylog2-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.graylog2:graylog2-server to 6.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7g5-jq6p-6wvx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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