How severe is GHSA-r9g5-7q8j-958c?

No CVSS score has been assigned to GHSA-r9g5-7q8j-958c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r9g5-7q8j-958c?

GHSA-r9g5-7q8j-958c affects the following packages: fuxa-server (npm). Ecosystems affected: npm.

How do I fix GHSA-r9g5-7q8j-958c?

Update fuxa-server to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9g5-7q8j-958c is resolved across your whole dependency graph.

How do I detect GHSA-r9g5-7q8j-958c in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-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.

How do I mitigate GHSA-r9g5-7q8j-958c 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.

How does O3 Security protect against GHSA-r9g5-7q8j-958c?

O3 pinpoints whether GHSA-r9g5-7q8j-958c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r9g5-7q8j-958c actively exploited in the wild?

No public exploit code has been indexed for GHSA-r9g5-7q8j-958c 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-r9g5-7q8j-958c?

GHSA-r9g5-7q8j-958c has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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-r9g5-7q8j-958c?

GHSA-r9g5-7q8j-958c is classified as Improper Authentication (CWE-287), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r9g5-7q8j-958c published, and has it been updated?

GHSA-r9g5-7q8j-958c was published on May 28, 2026 and was last updated on May 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-r9g5-7q8j-958c

GHSA-r9g5-7q8j-958c is a Improper Authentication vulnerability in fuxa-server. O3 Security confirms whether GHSA-r9g5-7q8j-958c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

FUXA provides guest and invalid-token access to protected read APIs in secure mode

Also known asCVE-2026-47718

Published

May 28, 2026

Updated

May 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-r9g5-7q8j-958c.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

fuxa-servernpm

11downloads / week

Description

Summary

When secureEnabled=true, FUXA 1.3.0-2773 still allows guest and invalid-token requests to read project, alarms, and scheduler APIs.

Details

In secure mode, requests with no token or an explicitly invalid token were still able to access protected read endpoints.

Confirmed behavior:

guest GET /api/project returned 200 OK
invalid-token requests to /api/project also returned successful responses containing project data
guest and invalid-token requests also returned 200 OK on:
- /api/alarms
- /api/scheduler

Relevant code paths identified during analysis:

server/api/jwt-helper.js
- verifyToken() converts missing-token or invalid-token states into guest context instead of rejecting the request
server/api/projects/index.js
server/api/alarms/index.js
server/api/scheduler/index.js

These handlers accepted the guest context and returned sensitive data in secure mode.

PoC

Tested only against isolated local lab instances under the original tester's control. No production, customer, shared, or third-party systems were involved.

Reproduction:

Start FUXA 1.3.0-2773.
Set secureEnabled=true.
Send unauthenticated requests to:
- GET /api/project
- GET /api/alarms
- GET /api/scheduler?id=test
Observe 200 OK responses.
Send the same requests with an explicitly invalid x-access-token value.
Observe the same successful responses.

The exact HTTP requests and local PoC script used for confirmation can be provided upon request.

Impact

This is an authentication/authorization weakness in secure mode.

Impact includes:

project metadata disclosure
alarms disclosure
scheduler information disclosure
assistance in reconnaissance/follow-on attacks

Operators who believe secure mode protects these APIs are impacted.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`fuxa-server`	≥ 1.3.0-2773&&< 1.3.1	1.3.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-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 fuxa-server to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9g5-7q8j-958c 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-r9g5-7q8j-958c 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-r9g5-7q8j-958c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. ### Details In secure mode, requests with no token or an explicitly invalid token were still able to access protected read endpoints. Confirmed behavior: - guest `GET /api/project` returned `200 OK` - invalid-token requests to `/api/project` also returned successful responses containing project data - guest and invalid-token requests also returned `200 OK` on: - `/api/alarms` - `/api/scheduler` Relevant code paths iden

O3 Security · Impact-Aware SCA

Is GHSA-r9g5-7q8j-958c in your dependencies?

O3 detects GHSA-r9g5-7q8j-958c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works