How severe is CVE-2008-6566?

CVE-2008-6566 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2008-6566 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2008-6566?

CVE-2008-6566 affects Octopussy. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2008-6566?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2008-6566 published?

CVE-2008-6566 was published on 2009-03-31 and last updated on 2026-06-16.

CVE-2008-6566

CVE-2008-6566 is a critical-severity vulnerability in Octopussy with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (73rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Octopussy
Published: 2009-03-31
Last modified: 2026-06-16

Description

Unspecified vulnerability in Octopussy before 0.9.5.8 has unknown impact and attack vectors related to a "major security" vulnerability.

Frequently asked questions

What is CVE-2008-6566?: Unspecified vulnerability in Octopussy before 0.9.5.8 has unknown impact and attack vectors related to a "major security" vulnerability.
How severe is CVE-2008-6566?: CVE-2008-6566 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2008-6566 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-6566?: CVE-2008-6566 affects Octopussy. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2008-6566?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2008-6566 published?: CVE-2008-6566 was published on 2009-03-31 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:octopussy:octopussy:*:*:*:*:*:*:*:*