ipycache is vulnerable to Code Injection

published 2019-03-21 7 y ago modified 2026-06-17 4 mo ago also GHSA-gcm4-q2pg-xw89 , PYSEC-2019-180 , EUVD-2019-0066

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

A code injection issue was discovered in ipycache through 2016-05-31.

Patch / fix

links 2

github.com/adi928/ipycache@9cc7cb8 commit
github.com/adi928/ipycache@c73a726 commit

Exploit prediction

1.60% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/rossant/ipycache/issues/47 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.1	9.6	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	ipycache	<=0.1.4 all versions	no fix listed

Classification

Weakness

CWE-502 Deserialization of Untrusted Data
CWE-94 Improper Control of Generation of Code

References

github.com /adi928/ipycache/commit/9cc7cb891ff169b3e8a6f5e84afd8238f566ad8e
web
github.com /adi928/ipycache/commit/c73a726744c90cc2cb200b159edbaf5deddcb753
web
github.com /rossant/ipycache/issues/47
web, exploit, third-party-advisory, report
nvd.nist.gov /vuln/detail/CVE-2019-7539
advisory
github.com /advisories/GHSA-gcm4-q2pg-xw89
advisory
github.com /pypa/advisory-database/tree/main/vulns/ipycache/PYSEC-2019-180.yaml
web
github.com /rossant/ipycache
package

Sources

Fencer Vulns 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