GHSA-9h33-g3ww-mqff is a high-severity (CVSS 7.1) Open Redirect vulnerability in github.com/pocket-id/pocket-id/backend. A fix is available for github.com/pocket-id/pocket-id/backend — see the affected versions and patch details below.
Pocket ID: OAuth redirect_uri validation bypass via userinfo/host confusion
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-9h33-g3ww-mqff.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-9h33-g3ww-mqff plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/pocket-id/pocket-id/backendReal-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
Impact
A flaw in callback URL validation allowed crafted redirect_uri values containing URL userinfo (@) to bypass legitimate callback pattern checks. If an attacker can trick a user into opening a malicious authorization link, the authorization code may be redirected to an attacker-controlled host.
Patches
Fixed in v2.3.1 (commit 3a339e33191c31b68bf57db907f800d9de5ffbc8).
The fix replaces delimiter-based callback matching with structured URL pattern matching and updates validation logic/tests.
Workarounds
- Reject callback URLs containing userinfo (
@) at reverse proxy / app policy level if feasible.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pocket-id/pocket-id/backend | all versions | 0.0.0-20260228130835-3a339e33191cgo get github.com/pocket-id/pocket-id/backend@v0.0.0-20260228130835-3a339e33191c |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pocket-id/pocket-id/backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pocket-id/pocket-id/backend to 0.0.0-20260228130835-3a339e33191c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9h33-g3ww-mqff 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9h33-g3ww-mqff can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9h33-g3ww-mqff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9h33-g3ww-mqff in your dependencies?
O3 Security finds GHSA-9h33-g3ww-mqff across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.