CVE-2017-7506: spice versions though 0.13 are vulnerable to out-of-bounds memory access when processing specially crafted mes

This month

HIGH 8.8DOWNGRADE

CVE-2017-7506 is a high-severity flaw (CVSS 8.8) affecting spice. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

spice versions though 0.13 are vulnerable to out-of-bounds memory access when processing specially crafted messages from authenticated attacker to the spice server resulting into crash and/or server memory leak.

Why this priority

High severity
EPSS top 9%: very likely to be exploited

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	4.2% (top 9%)
CISA exploited list	No
Weakness	CWE-119
Published	2017-07-18
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: spice project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-07-18 15:29 UTCPublished CVE record published
2026-06-17 01:24 UTCUpdated Record last modified

spice project spice DOWNGRADE

Affected: 0.5.2 · 0.5.3 · 0.6.0 · 0.6.1 · 0.6.2 · 0.6.3 · 0.6.4 · 0.7.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.5.2

1. Check installed version

apt-cache policy spice || rpm -q spice || spice --version

2. No fixed release: DOWNGRADE to a release before 0.5.2 (Debian / Ubuntu)

apt-cache madison spice sudo apt install spice=<VERSION_BEFORE_0.5.2> sudo apt-mark hold spice

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spice sudo dnf downgrade spice-<VERSION_BEFORE_0.5.2> sudo dnf versionlock add spice

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-7506?

spice: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-7506 being exploited?

CVE-2017-7506 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-7506 affect?

CVE-2017-7506 affects spice. Severity is high (CVSS 8.8). spice versions though 0.13 are vulnerable to out-of-bounds memory access when processing specially crafted messages from authenticated attacker to the spice server resulting into crash and/or server memory leak.

How urgent is CVE-2017-7506?

Priority 54/100. High severity; EPSS top 9%: very likely to be exploited

Related CVEs

CVE-2021-20201 MEDIUM 5.3 UPGRADE MITIGATE A flaw was found in spice in versions before 0.14.92
CVE-2020-14355 MEDIUM 6.6 UPGRADE DOWNGRADE Multiple buffer overflow vulnerabilities were found in the QUIC image decoding process of the SPICE remote dis
CVE-2019-3813 HIGH 7.5 UPGRADE MITIGATE Spice, versions 0.5.2 through 0.14.1, are vulnerable to an out-of-bounds read due to an off-by-one error in me
CVE-2018-10893 HIGH 7.6 MITIGATE Multiple integer overflow and buffer overflow issues were discovered in spice-client's handling of LZ compress
CVE-2018-10873 HIGH 8.3 UPGRADE MITIGATE A vulnerability was discovered in SPICE before version 0.14.1 where the generated code used for demarshalling

References

← Back to latest CVEs