GHSA-c8m8-3jcr-6rj5
HIGHGHSA-c8m8-3jcr-6rj5 is a high-severity (CVSS 8.1) Hard-coded Credentials vulnerability in @frangoteam/fuxa. O3 Security confirms whether GHSA-c8m8-3jcr-6rj5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
FUXA has a hardcoded fallback JWT signing secret
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@frangoteam/fuxanpmDescription
FUXA used a static fallback JWT signing secret (frangoteam751) when no secretCode was configured.
If authentication was enabled without explicitly setting a custom secret, an attacker who knew the default value could forge valid JWT tokens and bypass authentication.
This issue has been addressed in version 1.3.0 by removing the static fallback and generating a secure random secret when no secretCode is provided.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @frangoteam/fuxa | all versions | 1.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @frangoteam/fuxa. 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 @frangoteam/fuxa to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8m8-3jcr-6rj5 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-c8m8-3jcr-6rj5 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-c8m8-3jcr-6rj5. 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-c8m8-3jcr-6rj5 in your dependencies?
O3 detects GHSA-c8m8-3jcr-6rj5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.