Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-22617: Ardour v5.12 contains a use-after-free vulnerability in the component ardour/libs/pbd/xml++.cc when using xmlF

57
This month
CRITICAL 9.8REMOTEDOWNGRADE

CVE-2020-22617 is a critical-severity flaw (CVSS 9.8) affecting ardour. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Ardour v5.12 contains a use-after-free vulnerability in the component ardour/libs/pbd/xml++.cc when using xmlFreeDoc and xmlXPathFreeContext.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

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

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.3% (top 30%)
CISA exploited listNo
WeaknessCWE-416
Published2021-10-08
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: ardour

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

ardour ardour DOWNGRADE
Affected: 5.12
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.12
1. Check installed version
apt-cache policy ardour || rpm -q ardour || ardour --version
2. No fixed release: DOWNGRADE to a release before 5.12 (Debian / Ubuntu)
apt-cache madison ardour sudo apt install ardour=<VERSION_BEFORE_5.12> sudo apt-mark hold ardour
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list ardour sudo dnf downgrade ardour-<VERSION_BEFORE_5.12> sudo dnf versionlock add ardour
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-2020-22617?

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

Is CVE-2020-22617 being exploited?

CVE-2020-22617 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-2020-22617 affect?

CVE-2020-22617 affects ardour. Severity is critical (CVSS 9.8). Ardour v5.12 contains a use-after-free vulnerability in the component ardour/libs/pbd/xml++.cc when using xmlFreeDoc and xmlXPathFreeContext.

How urgent is CVE-2020-22617?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.