What is CVE-2024-24556?

CVE-2024-24556 is a high-severity cross-site scripting (XSS) vulnerability in @urql/next (npm), affecting versions < 1.1.1. It is fixed in 1.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2024-24556?

CVE-2024-24556 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @urql/next are affected by CVE-2024-24556?

@urql/next (npm) versions < 1.1.1 is affected.

Is there a fix for CVE-2024-24556?

Yes. CVE-2024-24556 is fixed in 1.1.1. Upgrade to this version or later.

Is CVE-2024-24556 exploitable, and should I be worried?

Whether CVE-2024-24556 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-24556 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-24556 in @urql/next

Q: How severe is CVE-2024-24556?

CVE-2024-24556 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @urql/next are affected by CVE-2024-24556?

@urql/next (npm) versions < 1.1.1 is affected.

Q: Is there a fix for CVE-2024-24556?

Yes. CVE-2024-24556 is fixed in 1.1.1. Upgrade to this version or later.

Q: Is CVE-2024-24556 exploitable, and should I be worried?

Whether CVE-2024-24556 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-24556 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-24556?

Upgrade @urql/next to 1.1.1 or later.

Summary

@urql/next Cross-site Scripting vulnerability

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

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-24556 has a CVSS score of 7.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.1); upgrading removes the vulnerable code path.

Affected versions

@urql/next (< 1.1.1)

Security releases

@urql/next → 1.1.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade @urql/next to 1.1.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-24556? CVE-2024-24556 is a high-severity cross-site scripting (XSS) vulnerability in @urql/next (npm), affecting versions < 1.1.1. It is fixed in 1.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2024-24556? CVE-2024-24556 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @urql/next are affected by CVE-2024-24556? @urql/next (npm) versions < 1.1.1 is affected.
Is there a fix for CVE-2024-24556? Yes. CVE-2024-24556 is fixed in 1.1.1. Upgrade to this version or later.
Is CVE-2024-24556 exploitable, and should I be worried? Whether CVE-2024-24556 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-24556 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-24556? Upgrade @urql/next to 1.1.1 or later.