What CVEs are caused by CWE-610?

68 recorded CVEs are attributed to CWE-610, including CVE-2022-27593, CVE-2017-16088, CVE-2022-39206. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

What are the consequences of CWE-610?

Exploiting CWE-610 can lead to: Read Application Data, Modify Application Data, Gain Privileges or Assume Identity.

Is CWE-610 actively exploited?

Yes. 1 CWE-610 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 68 recorded CVEs.

Class weakness

Draft

CWE-610: Externally Controlled Reference to a Resource in Another Sphere

The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

Last updated May 1, 2026

Recorded CVEs

With this primary weakness

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Class

Abstraction

MITRE classification

Overview

CWE-610 (Externally Controlled Reference to a Resource in Another Sphere) is a class-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.

Real-world CVEs

68 recorded CVEs are caused by CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), including 1 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 14 new CWE-610 CVEs have been recorded so far in 2026 (14 in 2025).

Showing 12 of 68 recorded CWE-610 CVEs. Track new ones as they are published and get AI-written analysis and fixes.

Monitor CWE-610 vulnerabilities

Common consequences

What can happen when CWE-610 is exploited.

Read Application Data, Modify Application Data

Affects: Confidentiality, Integrity

An adversary could read or modify data, depending on how the resource is intended to be used.

Gain Privileges or Assume Identity

Affects: Access Control

An adversary that can supply a reference to an unintended resource can potentially access a resource that they do not have privileges for, thus bypassing existing access control mechanisms.

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Code examples

Illustrative examples from MITRE showing how the weakness appears in code.

The following code is a Java servlet that will receive a GET request with a url parameter in the request to redirect the browser to the address specified in the url parameter. The servlet will retrieve the url parameter value from the request and send a response to redirect the browser to the url address.

Vulnerable example

java

public class RedirectServlet extends HttpServlet {

Attack input

xml

<a href="http://bank.example.com/redirect?url=http://attacker.example.net">Click here to log in</a>

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2022-3032 — An email client does not block loading of remote objects in a nested document.
CVE-2022-45918 — Chain: a learning management tool debugger uses external input to locate previous session logs (CWE-73) and does not properly validate the given path (CWE-20), allowing for filesystem path traversal using "../" sequences (CWE-24)
CVE-2018-1000613 — Cryptography API uses unsafe reflection when deserializing a private key
CVE-2020-11053 — Chain: Go-based Oauth2 reverse proxy can send the authenticated user to another site at the end of the authentication flow. A redirect URL with HTML-encoded whitespace characters can bypass the validation (CWE-1289) to redirect to a malicious site (CWE-601)
CVE-2022-42745 — Recruiter software allows reading arbitrary files using XXE
CVE-2004-2331 — Database system allows attackers to bypass sandbox restrictions by using the Reflection API.

Attack patterns

CAPEC attack patterns that exploit this weakness.

CAPEC-219: XML Routing Detour Attacks

Frequently asked questions

Common questions about CWE-610.

What is CWE-610?: The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
What CVEs are caused by CWE-610?: 68 recorded CVEs are attributed to CWE-610, including CVE-2022-27593, CVE-2017-16088, CVE-2022-39206. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
What are the consequences of CWE-610?: Exploiting CWE-610 can lead to: Read Application Data, Modify Application Data, Gain Privileges or Assume Identity.
Is CWE-610 actively exploited?: Yes. 1 CWE-610 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 68 recorded CVEs.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-610

Get alerted the moment a new CWE-610 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing