How severe is CVE-2015-0259?

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

Which packages are affected by CVE-2015-0259?

CVE-2015-0259 affects the following packages: nova (PyPI), nova (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-0259?

Update nova to 2014.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0259 is resolved across your whole dependency graph.

How do I detect CVE-2015-0259 in my PyPI dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2015-0259 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-0259 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-2015-0259?

CVE-2015-0259 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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-2015-0259?

CVE-2015-0259 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-0259 published, and has it been updated?

CVE-2015-0259 was published on April 1, 2015 and was last updated on July 7, 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

CVE-2015-0259 — nova

CVE-2015-0259 is a CWE-345 vulnerability in nova. A fix is available for nova — see the affected versions and patch details below.

OpenStack Compute (Nova) has Insufficient Verification of Data Authenticity

Also known asGHSA-x8xr-rm9r-7mvfPYSEC-2026-883

Published

Apr 1, 2015

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐍nova🐍nova

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

OpenStack Compute (Nova) before 2014.1.4, 2014.2.x before 2014.2.3, and kilo before kilo-3 does not validate the origin of websocket requests, which allows remote attackers to hijack the authentication of users for access to consoles via a crafted webpage.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nova`	all versions	2014.1.4`pip install --upgrade 'nova==2014.1.4'`
🐍PyPI	`nova`	≥ 2014.2.0&&< 2014.2.3	2014.2.3`pip install --upgrade 'nova==2014.2.3'`

Affected Products

1 product · 4 configurations

Application

novaopenstack

≥ 2014.2 && < 2014.2.3

1 version

2015.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nova, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nova to 2014.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-0259 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6	`openstack-nova-0:2014.1.4-3.el6ost`	RHSA-2015:0844
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7	`openstack-nova-0:2014.1.4-3.el7ost`	RHSA-2015:0843
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-nova-0:2014.2.2-19.el7ost`	RHSA-2015:0790

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-0259 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works