How severe is CVE-2013-4221?

No CVSS score has been assigned to CVE-2013-4221 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4221?

CVE-2013-4221 affects the following packages: org.restlet.jse:org.restlet (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4221?

Update org.restlet.jse:org.restlet to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4221 is resolved across your whole dependency graph.

How do I detect CVE-2013-4221 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.restlet.jse:org.restlet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4221 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2013-4221 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4221 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 is the EPSS score for CVE-2013-4221?

CVE-2013-4221 has an EPSS (Exploit Prediction Scoring System) score of 3.4%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4221?

CVE-2013-4221 is classified as CWE-16 (CWE-16), CWE-91 (CWE-91). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-4221 published, and has it been updated?

CVE-2013-4221 was published on May 17, 2022 and was last updated on March 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-4221 — org.restlet

Fix: restlet/restlet-framework-java@b85c2ef

CVE-2013-4221 is a CWE-16 vulnerability in org.restlet.jse:org.restlet. A fix is available for org.restlet.jse:org.restlet — see the affected versions and patch details below.

Restlet is vulnerable to Arbitrary Java Code Execution via crafted XML

Published

May 17, 2022

Updated

Mar 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.4%probability of exploitation in next 30 days

Lower Risk+0.49%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.restlet.jse:org.restlet

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

Description

The default configuration of the ObjectRepresentation class in Restlet before 2.1.4 deserializes objects from untrusted sources using the Java XMLDecoder, which allows remote attackers to execute arbitrary Java code via crafted XML.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.restlet.jse:org.restlet`	all versions	2.1.4`org.restlet.jse:org.restlet:2.1.4`

Affected Products

1 product · 16 configurations

Application

restletrestlet

≤ 2.1.3

4 versions

2.12.1.02.1.12.1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.restlet.jse:org.restlet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.restlet.jse:org.restlet to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4221 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4221 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works