CVE-2015-5607

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 35% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

Cross-site request forgery in the REST API in IPython 2 and 3.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
66%
KEV
Not listed

Published

September 20, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
Patch available. Sources: redhat, github_commit.
redhat Patch Available

1243842 – (CVE-2015-5607) CVE-2015-5607 iptyhon: cross-site request forgery in get_origin()

https://bugzilla.redhat.com/show_bug.cgi?id=1243842
generic

oss-security - Re: CVE request: IPython CSRF validation

http://www.openwall.com/lists/oss-security/2015/07/21/3
github_commit

commit a05fe052a188 (ipython/ipython)

Fix landed in ipython/ipython commit a05fe052a188 — awaiting tagged release

https://github.com/ipython/ipython/commit/a05fe052a18810e92d9be8c1185952c13fe4e5b0
github_commit

commit 1415a9710407 (ipython/ipython)

Fix landed in ipython/ipython commit 1415a9710407 — awaiting tagged release

https://github.com/ipython/ipython/commit/1415a9710407e7c14900531813c15ba6165f0816

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuipython3 (5.5.0-1ubuntu0.1~esm1) @ bionic2026-05-22ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ipython—2.4.1-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ipython—2.4.1-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ipython—2.4.1-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ipython—2.4.1-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
ipython0.10 ... 3.2.0 (48 versions)3.2.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-08-25 13:44 UTCEPSS rescore
  2. 2026-08-23 00:13 UTCEPSS rescore
  3. 2026-08-21 23:44 UTCEPSS rescore
  4. 2026-08-20 22:50 UTCEPSS rescore
  5. 2026-08-19 16:59 UTCEPSS rescore
  6. 2026-08-18 13:43 UTCEPSS rescore
  7. 2026-08-16 14:51 UTCEPSS rescore
  8. 2026-08-16 02:09 UTCEPSS rescore
  9. 2026-08-15 01:25 UTCEPSS rescore
  10. 2026-08-13 22:39 UTCOSV refresh
  11. 2026-08-12 13:46 UTCEPSS rescore
  12. 2026-08-11 13:36 UTCEPSS rescore
  13. 2026-08-09 13:42 UTCEPSS rescore
  14. 2026-08-08 16:32 UTCEPSS rescore
  15. 2026-08-07 16:22 UTCEPSS rescore
  16. 2026-08-06 13:42 UTCEPSS rescore
  17. 2026-08-05 19:12 UTCEPSS rescore
  18. 2026-08-04 15:04 UTCEPSS rescore
  19. 2026-08-04 10:31 UTCEPSS rescore
  20. 2026-08-01 04:11 UTCEPSS rescore
  21. 2026-07-30 01:26 UTCEPSS rescore
  22. 2026-07-30 01:26 UTCEPSS rescore
  23. 2026-07-29 01:21 UTCOSV refresh
  24. 2026-07-28 15:31 UTCEPSS rescore
  25. 2026-07-26 14:50 UTCEPSS rescore
Show 75 more
  1. 2026-07-25 14:13 UTCEPSS rescore
  2. 2026-07-23 14:14 UTCEPSS rescore
  3. 2026-07-23 01:18 UTCEG score recompute
  4. 2026-07-23 00:20 UTCEG score recompute
  5. 2026-07-22 21:59 UTCEG score recompute
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-19 14:27 UTCEPSS rescore
  11. 2026-07-19 14:27 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-18 10:00 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-15 01:56 UTCEPSS rescore
  19. 2026-07-13 22:26 UTCEPSS rescore
  20. 2026-07-13 22:26 UTCEPSS rescore
  21. 2026-07-12 05:42 UTCEPSS rescore
  22. 2026-07-11 17:52 UTCOSV refresh
  23. 2026-07-11 08:23 UTCEPSS rescore
  24. 2026-07-09 19:05 UTCEPSS rescore
  25. 2026-07-09 19:05 UTCEPSS rescore
  26. 2026-07-08 15:10 UTCEPSS rescore
  27. 2026-07-07 13:42 UTCEPSS rescore
  28. 2026-07-07 13:42 UTCEPSS rescore
  29. 2026-07-06 16:24 UTCEPSS rescore
  30. 2026-07-06 02:20 UTCEPSS rescore
  31. 2026-07-05 02:26 UTCEPSS rescore
  32. 2026-07-04 06:28 UTCEPSS rescore
  33. 2026-07-01 15:02 UTCEPSS rescore
  34. 2026-06-30 23:19 UTCEPSS rescore
  35. 2026-06-30 23:19 UTCEPSS rescore
  36. 2026-06-29 14:03 UTCEPSS rescore
  37. 2026-06-29 14:03 UTCEPSS rescore
  38. 2026-06-28 14:04 UTCEPSS rescore
  39. 2026-06-28 04:53 UTCEPSS rescore
  40. 2026-06-27 03:05 UTCEPSS rescore
  41. 2026-06-25 13:47 UTCEPSS rescore
  42. 2026-06-25 13:47 UTCEPSS rescore
  43. 2026-06-24 14:02 UTCEPSS rescore
  44. 2026-06-24 14:02 UTCEPSS rescore
  45. 2026-06-23 21:30 UTCEPSS rescore
  46. 2026-06-23 00:00 UTCOSV refresh
  47. 2026-06-22 14:23 UTCEPSS rescore
  48. 2026-06-22 14:23 UTCEPSS rescore
  49. 2026-06-21 14:54 UTCEPSS rescore
  50. 2026-06-21 14:54 UTCEPSS rescore
  51. 2026-06-21 01:57 UTCEPSS rescore
  52. 2026-06-21 01:57 UTCEPSS rescore
  53. 2026-06-19 19:23 UTCEPSS rescore
  54. 2026-06-19 19:23 UTCEPSS rescore
  55. 2026-06-18 17:50 UTCEPSS rescore
  56. 2026-06-17 17:50 UTCEPSS rescore
  57. 2026-06-17 17:49 UTCEPSS rescore
  58. 2026-06-16 17:50 UTCEPSS rescore
  59. 2026-06-16 17:50 UTCEPSS rescore
  60. 2026-06-15 17:45 UTCEPSS rescore
  61. 2026-06-14 23:14 UTCEPSS rescore
  62. 2026-06-13 22:57 UTCEPSS rescore
  63. 2026-06-12 23:09 UTCEPSS rescore
  64. 2026-06-12 23:09 UTCEPSS rescore
  65. 2026-06-11 13:57 UTCEPSS rescore
  66. 2026-06-11 13:57 UTCEPSS rescore
  67. 2026-06-10 22:15 UTCEPSS rescore
  68. 2026-06-10 13:18 UTCEPSS rescore
  69. 2026-06-08 14:14 UTCEPSS rescore
  70. 2026-06-07 15:22 UTCEPSS rescore
  71. 2026-06-06 13:45 UTCEPSS rescore
  72. 2026-06-05 22:44 UTCEPSS rescore
  73. 2026-06-05 18:27 UTCOSV refresh
  74. 2026-06-05 06:08 UTCEPSS rescore
  75. 2026-06-05 06:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2015-5607?
CVE-2015-5607 is a high vulnerability published on September 20, 2017. Cross-site request forgery in the REST API in IPython 2 and 3.
When was CVE-2015-5607 disclosed?
CVE-2015-5607 was first published in the National Vulnerability Database on September 20, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-5607 actively exploited?
CVE-2015-5607 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 33.8% of all scored CVEs.
What is the CVSS score of CVE-2015-5607?
CVE-2015-5607 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2015-5607?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-5607, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-5607

Explore →

Is Your Infrastructure Affected by CVE-2015-5607?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs