How severe is GHSA-qhjf-hm5j-335w?

GHSA-qhjf-hm5j-335w has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qhjf-hm5j-335w?

GHSA-qhjf-hm5j-335w affects the following packages: @urql/next (npm). Ecosystems affected: npm.

How do I fix GHSA-qhjf-hm5j-335w?

Update @urql/next to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhjf-hm5j-335w is resolved across your whole dependency graph.

How do I detect GHSA-qhjf-hm5j-335w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @urql/next. 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-qhjf-hm5j-335w 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-qhjf-hm5j-335w?

O3 pinpoints whether GHSA-qhjf-hm5j-335w 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-qhjf-hm5j-335w actively exploited in the wild?

No public exploit code has been indexed for GHSA-qhjf-hm5j-335w 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 type of vulnerability is GHSA-qhjf-hm5j-335w?

GHSA-qhjf-hm5j-335w is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qhjf-hm5j-335w published, and has it been updated?

GHSA-qhjf-hm5j-335w was published on January 30, 2024 and was last updated on January 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-qhjf-hm5j-335w

HIGH

GHSA-qhjf-hm5j-335w is a high-severity (CVSS 7.2) Cross-site Scripting (XSS) vulnerability in @urql/next. O3 Security confirms whether GHSA-qhjf-hm5j-335w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@urql/next Cross-site Scripting vulnerability

Also known asCVE-2024-24556

Published

Jan 30, 2024

Updated

Jan 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@urql/nextnpm

52Kdownloads / week

Description

impact

The @urql/next package is vulnerable to XSS. To exploit this an attacker would need to ensure that the response returns html tags and that the web-application is using streamed responses (non-RSC). This vulnerability is due to improper escaping of html-like characters in the response-stream.

To fix this vulnerability upgrade to version 1.1.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@urql/next`	all versions	1.1.1

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

## impact The `@urql/next` package is vulnerable to XSS. To exploit this an attacker would need to ensure that the response returns `html` tags and that the web-application is using streamed responses (non-RSC). This vulnerability is due to improper escaping of html-like characters in the response-stream. To fix this vulnerability upgrade to version 1.1.1

O3 Security · Impact-Aware SCA

Is GHSA-qhjf-hm5j-335w in your dependencies?

O3 detects GHSA-qhjf-hm5j-335w 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