GHSA-wx8q-rgfr-cf6v
MEDIUMGHSA-wx8q-rgfr-cf6v is a medium-severity (CVSS 6.5) CWE-284 vulnerability in github.com/google/exposure-notifications-verification-server. O3 Security confirms whether GHSA-wx8q-rgfr-cf6v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insufficient Granularity of Access Control in github.com/google/exposure-notifications-verification-server
Real-World Exposure
github.com/google/exposure-notifications-verification-serverReal-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
Users or API keys with permission to expire verification codes could have expired codes that belonged to another realm if they guessed the UUID.
Patches
v1.1.2+
Workarounds
There are no workarounds, and there are no indications this has been exploited in the wild. Verification codes can only be expired by providing their 64-bit UUID, and verification codes are already valid for a very short period of time (thus the UUID rotates frequently).
For more information
Contact [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/google/exposure-notifications-verification-server | all versions | 1.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/exposure-notifications-verification-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/google/exposure-notifications-verification-server to 1.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wx8q-rgfr-cf6v 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 pinpoints whether GHSA-wx8q-rgfr-cf6v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wx8q-rgfr-cf6v. 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-wx8q-rgfr-cf6v in your dependencies?
O3 detects GHSA-wx8q-rgfr-cf6v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.