How severe is GHSA-q9rr-h3hx-m87g?

No CVSS score has been assigned to GHSA-q9rr-h3hx-m87g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q9rr-h3hx-m87g?

GHSA-q9rr-h3hx-m87g affects the following packages: github.com/bunkerity/bunkerweb (Go). Ecosystems affected: Go.

How do I fix GHSA-q9rr-h3hx-m87g?

Update github.com/bunkerity/bunkerweb to 1.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9rr-h3hx-m87g is resolved across your whole dependency graph.

How do I detect GHSA-q9rr-h3hx-m87g in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bunkerity/bunkerweb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q9rr-h3hx-m87g if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-q9rr-h3hx-m87g actively exploited in the wild?

No public exploit code has been indexed for GHSA-q9rr-h3hx-m87g 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-q9rr-h3hx-m87g?

GHSA-q9rr-h3hx-m87g has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-q9rr-h3hx-m87g?

GHSA-q9rr-h3hx-m87g is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q9rr-h3hx-m87g published, and has it been updated?

GHSA-q9rr-h3hx-m87g was published on December 2, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

BunkerWeb has Open Redirect Vulnerability in Loading PageGHSA-q9rr-h3hx-m87g

GHSA-q9rr-h3hx-m87g is a Open Redirect vulnerability in github.com/bunkerity/bunkerweb. A fix is available for github.com/bunkerity/bunkerweb — see the affected versions and patch details below.

Also known asCVE-2024-53264GO-2024-3294

Published

Dec 2, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 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-q9rr-h3hx-m87g.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐹github.com/bunkerity/bunkerweb

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

Description

bunkerweb is an Open-source and next-generation Web Application Firewall (WAF). A open redirect vulnerability exists in the loading endpoint, allowing attackers to redirect authenticated users to arbitrary external URLs via the "next" parameter. The loading endpoint accepts and uses an unvalidated "next" parameter for redirects. Ex. visiting: /loading?next=https://google.com while authenticated will cause the page will redirect to google.com. This vulnerability could be used in phishing attacks by redirecting users from a legitimate application URL to malicious sites. This issue has been addressed in version 1.5.11. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bunkerity/bunkerweb`	all versions	1.5.11`go get github.com/bunkerity/bunkerweb@v1.5.11`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bunkerity/bunkerweb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bunkerity/bunkerweb to 1.5.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9rr-h3hx-m87g is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### Summary: A open redirect vulnerability exists in the loading endpoint, allowing attackers to redirect authenticated users to arbitrary external URLs via the "next" parameter. ### Details: The loading endpoint accepts and uses an unvalidated "next" parameter for redirects: ### PoC: Visit: `/loading?next=https://google.com` while authenticated. The page will redirect to google.com. ### Impact: This vulnerability could be used in phishing attacks by redirecting users from a legitimate application URL to malicious sites.

O3 Security · Impact-Aware SCA

Is GHSA-q9rr-h3hx-m87g in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works