CVE-2001-1566: Format string vulnerability in libvanessa_logger 0.0.1 in Perdition 0.1.8 allows remote attackers to execute a

This month

HIGH 7.5DOWNGRADEDOWNGRADE

CVE-2001-1566 is a high-severity flaw (CVSS 7.5) affecting vanessa logger, perdition. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Format string vulnerability in libvanessa_logger 0.0.1 in Perdition 0.1.8 allows remote attackers to execute arbitrary code via format string specifiers in the __vanessa_logger_log function.

Why this priority

High severity

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.8% (top 14%)
CISA exploited list	No
Published	2001-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: vanessa · verge

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

Am I affected?

Timeline

2001-12-31 05:00 UTCPublished CVE record published
2026-06-16 21:56 UTCUpdated Record last modified

vanessa vanessa logger DOWNGRADE

Affected: 0.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.1

1. Check installed version

apt-cache policy vanessa-logger || rpm -q vanessa-logger || vanessa-logger --version

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

apt-cache madison vanessa-logger sudo apt install vanessa-logger=<VERSION_BEFORE_0.0.1> sudo apt-mark hold vanessa-logger

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

dnf --showduplicates list vanessa-logger sudo dnf downgrade vanessa-logger-<VERSION_BEFORE_0.0.1> sudo dnf versionlock add vanessa-logger

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.

verge perdition DOWNGRADE

Affected: 0.1.8

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.8

1. Check installed version

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

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

apt-cache madison perdition sudo apt install perdition=<VERSION_BEFORE_0.1.8> sudo apt-mark hold perdition

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

dnf --showduplicates list perdition sudo dnf downgrade perdition-<VERSION_BEFORE_0.1.8> sudo dnf versionlock add perdition

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-2001-1566?

vanessa logger: downgrade or apply the listed mitigation; perdition: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2001-1566 being exploited?

CVE-2001-1566 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-2001-1566 affect?

CVE-2001-1566 affects vanessa logger, perdition. Severity is high (CVSS 7.5). Format string vulnerability in libvanessa_logger 0.0.1 in Perdition 0.1.8 allows remote attackers to execute arbitrary code via format string specifiers in the __vanessa_logger_log function.

How urgent is CVE-2001-1566?

Priority 48/100. High severity

References

← Back to latest CVEs