How severe is GHSA-r7x9-8ph7-w8cg?

No CVSS score has been assigned to GHSA-r7x9-8ph7-w8cg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r7x9-8ph7-w8cg?

GHSA-r7x9-8ph7-w8cg affects the following packages: agents (npm). Ecosystems affected: npm.

How do I fix GHSA-r7x9-8ph7-w8cg?

Update agents to 0.3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7x9-8ph7-w8cg is resolved across your whole dependency graph.

How do I detect GHSA-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg?

O3 pinpoints whether GHSA-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg actively exploited in the wild?

No public exploit code has been indexed for GHSA-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg?

GHSA-r7x9-8ph7-w8cg is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r7x9-8ph7-w8cg published, and has it been updated?

GHSA-r7x9-8ph7-w8cg was published on February 3, 2026 and was last updated on February 22, 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-r7x9-8ph7-w8cg

GHSA-r7x9-8ph7-w8cg is a CWE-639 vulnerability in agents. O3 Security confirms whether GHSA-r7x9-8ph7-w8cg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cloudflare Agents SDK has Insecure Direct Object Reference (IDOR) via Header-Based Email Routing

Also known asCVE-2026-1664

Published

Feb 3, 2026

Updated

Feb 22, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

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.

agentsnpm

1.3Mdownloads / week

Description

Summary

An Insecure Direct Object Reference (CWE-639) has been found to exist in createHeaderBasedEmailResolver() function within the Cloudflare Agents SDK. The issue occurs because the Message-ID and References headers are parsed to derive the target agentName and agentId without proper validation or origin checks, allowing an external attacker with control of these headers to route inbound mail to arbitrary Durable Object instances and namespaces.

Root cause

The createHeaderBasedEmailResolver() function lacks cryptographic verification or origin validation for the headers used in the routing logic, effectively allowing external input to dictate internal object routing.

Impact

Insecure Direct Object Reference (IDOR) in email routing lets an attacker steer inbound mail to arbitrary Agent instances via spoofed Message-ID.

Patches

Agents-sdk users should upgrade to [email protected]. PR: https://github.com/cloudflare/agents/pull/811 This documentation provides the necessary architectural context for coding agents to mitigate the issue by refactoring the resolver to enforce strict identity boundaries.

Affected Packages

1 total 1 fixed

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

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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg 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-r7x9-8ph7-w8cg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An Insecure Direct Object Reference (CWE-639) has been found to exist in createHeaderBasedEmailResolver() function within the Cloudflare Agents SDK. The issue occurs because the Message-ID and References headers are parsed to derive the target agentName and agentId without proper validation or origin checks, allowing an external attacker with control of these headers to route inbound mail to arbitrary Durable Object instances and namespaces. ### Root cause The createHeaderBasedEmailResolver() function lacks cryptographic verification or origin validation for the headers used in th

O3 Security · Impact-Aware SCA

Is GHSA-r7x9-8ph7-w8cg in your dependencies?

O3 detects GHSA-r7x9-8ph7-w8cg 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