Code injection in rope

published 2018-04-06 8 y ago modified 2026-06-17 4 mo ago also GHSA-r38r-qp28-2m63 , PYSEC-2018-100 , EUVD-2018-0132

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.0%; EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits: 0; none known

base/oi/doa.py in the Rope library in CPython (aka Python) allows remote attackers to execute arbitrary code by leveraging an unsafe call to pickle.load.

Patch / fix

fixed in 2 distros 2 links 1

pypi rope 0.11.0
rope_project rope 0.11.0

debian opensuse

rope Debian 14, Debian 13, Debian 12 0.10.3-1

debian advisories DEBIAN-CVE-2014-3539

python-rope openSUSE Tumbleweed 1.14.0-1.4
python-rope openSUSE Tumbleweed 1.12.0-1.3
python-rope openSUSE Tumbleweed 0.10.2-2.2
python-rope openSUSE Tumbleweed 0.19.0-1.3

opensuse advisories openSUSE-SU-2026:12039-1 openSUSE-SU-2024:14161-1 openSUSE-SU-2024:10052-1 openSUSE-SU-2024:11267-1

github.com/python-rope/rope@b01da7a commit

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-3539 updated 2025-11-21 cvss 6.8

python-rope: pickle.load of remotely supplied data with no authentication required

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.97% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	rope	<0.11.0	0.11.0

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

github.com /python-rope/rope/commit/b01da7aab5cd02129941d2a900e6e5e3b5f7d4fb
web
openwall.com /lists/oss-security/2015/02/07/1
mailing-list, web, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=1116485
web, issue-tracking, third-party-advisory, report
nvd.nist.gov /vuln/detail/CVE-2014-3539
advisory
github.com /pypa/advisory-database/tree/main/vulns/rope/PYSEC-2018-100.yaml
web
github.com /python-rope/rope
package
github.com /advisories/GHSA-r38r-qp28-2m63
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary