How severe is CVE-2013-5093?

CVE-2013-5093 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2013-5093?

CVE-2013-5093 affects the following packages: graphite-web (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-5093?

Update graphite-web to 0.9.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5093 is resolved across your whole dependency graph.

How do I detect CVE-2013-5093 in my PyPI dependencies?

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

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

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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

Yes. There are 7 known exploit references for CVE-2013-5093, including 1 documented proof-of-concept exploit on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-5093?

CVE-2013-5093 has an EPSS (Exploit Prediction Scoring System) score of 38.8%, placing it in the 99th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2013-5093?

CVE-2013-5093 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2013-5093 was published on September 27, 2013 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2013-5093 — graphite-web

CRITICAL

CVE-2013-5093 is a critical-severity (CVSS 9) Code Injection vulnerability in graphite-web. 7 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for graphite-web — see the affected versions and patch details below.

graphite-web is vulnerable to Remote Code Execution via renderLocalView function

Also known asGHSA-m923-w2gj-v43gPYSEC-2013-3

Published

Sep 27, 2013

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

7 known

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

EPSS Exploitation Probability

via FIRST.org ↗

38.8%probability of exploitation in next 30 days

Moderate Risk+0.14%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍graphite-web

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

Description

The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`graphite-web`	≥ 0.9.5&&< 0.9.11	0.9.11`pip install --upgrade 'graphite-web==0.9.11'`

Affected Products

1 product · 6 configurations

Application

graphitegraphite_project

6 versions

0.9.50.9.60.9.70.9.80.9.90.9.10

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-27752remoteunix✓ Verified

Graphite Web - Unsafe Pickle Handling (Metasploit)

by Metasploit · Aug 21, 2013

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphite-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update graphite-web to 0.9.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5093 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-5093 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

CWE Classification

CWE-94Code Injection

Weaponization

No Nuclei template or Metasploit module yet. 7 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

graphite-web

5.0/10

Code-Review10/10

Maintained0/10

Branch-ProtectionN/A

Assessed Nov 2, 2026

Timeline

First exploit

Aug 21, 2013

Disclosed

Sep 27, 2013

Last updated

Apr 10, 2026

Identifiers

CVE-2013-5093

GHSA-m923-w2gj-v43g

PYSEC-2013-3

References

Advisorysecunia.com Advisorynvd.nist.gov · CVE 2013 5093 Webosvdb.org Webgithub.com · 0 9 11.rst Webgithub.com · PYSEC 2013 3.yaml Webweb.archive.org Webceriksen.com · graphite remote code execution vulnerability advisory Packagegithub.com · graphite web Evidenceceriksen.com · graphite remote code execution vulnerability advisory Evidenceexploit-db.com Evidencesecurityfocus.com Evidencegithub.com · 0 9 11.rst Evidencegithub.com · graphite pickle exec.rb

Related vulnerabilities

Also affects graphite-web

This CVE is critical severity; 1 of 5 other CVEs affecting graphite-web is rated as high or higher (top: critical).

CVE-2022-4728CVE-2022-4730CVE-2022-4729CVE-2013-5942CVE-2017-18638

Same weakness: CWE-94

This CVE is critical severity; 1 of 3 other CVEs with CWE-94 is rated as high or higher (top: critical).

CVE-2026-62284CVE-2026-61536CVE-2026-44267Browse all CWE-94

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026

CVE-2013-5093 — graphite-web

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2013-5093 in your dependencies?