How severe is GHSA-w5cr-2qhr-jqc5?

No CVSS score has been assigned to GHSA-w5cr-2qhr-jqc5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w5cr-2qhr-jqc5?

GHSA-w5cr-2qhr-jqc5 affects the following packages: agents (npm). Ecosystems affected: npm.

How do I fix GHSA-w5cr-2qhr-jqc5?

Update agents to 0.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5cr-2qhr-jqc5 is resolved across your whole dependency graph.

How do I detect GHSA-w5cr-2qhr-jqc5 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for agents. 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-w5cr-2qhr-jqc5 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-w5cr-2qhr-jqc5?

O3 pinpoints whether GHSA-w5cr-2qhr-jqc5 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-w5cr-2qhr-jqc5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w5cr-2qhr-jqc5 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.

When was GHSA-w5cr-2qhr-jqc5 published, and has it been updated?

GHSA-w5cr-2qhr-jqc5 was published on February 13, 2026 and was last updated on February 13, 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

GHSA-w5cr-2qhr-jqc5

Cloudflare Agents has a Reflected Cross-Site Scripting (XSS) vulnerability in AI Playground site

Published

Feb 13, 2026

Updated

Feb 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦agents

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A Reflected Cross-Site Scripting (XSS) vulnerability was discovered in the AI Playground's OAuth callback handler. The error_description query parameter was directly interpolated into an HTML script tag without proper escaping, allowing attackers to execute arbitrary JavaScript in the context of the victim's session.

Root cause

The OAuth callback handler in site/ai-playground/src/server.ts directly interpolated the authError value, sourced from the error_description query parameter, into an inline <script> tag.

Impact

An attacker could craft a malicious link that, when clicked by a victim, would:

Steal user chat message history
Access all LLM interactions stored in the user's session.
Access connected MCP Servers
Interact with any MCP servers connected to the victim's session (public or authenticated/private), potentially allowing the attacker to perform actions on the victim's behalf

Mitigation:

PR: https://github.com/cloudflare/agents/pull/841
Agents-sdk users should upgrade to [email protected]
Developers using configureOAuthCallback with custom error handling in their own applications should ensure all user-controlled input is escaped before interpolation.

Credits

Disclosed responsibly by Nishant Kumawat

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`agents`	all versions	0.3.10

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

## Summary A Reflected Cross-Site Scripting (XSS) vulnerability was discovered in the AI Playground's OAuth callback handler. The error_description query parameter was directly interpolated into an HTML script tag without proper escaping, allowing attackers to execute arbitrary JavaScript in the context of the victim's session. ### Root cause The OAuth callback handler in `site/ai-playground/src/server.ts` directly interpolated the `authError` value, sourced from the `error_description` query parameter, into an inline `<script>` tag. ### Impact An attacker could craft a malicious link th

O3 Security · Impact-Aware SCA

Is GHSA-w5cr-2qhr-jqc5 in your dependencies?

O3 detects GHSA-w5cr-2qhr-jqc5 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