Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-25643: seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid

60
This week
CRITICAL 9.8REMOTEUPGRADE

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

seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.1% (top 18%)
CISA exploited listNo
WeaknessCWE-668
Published2022-02-24
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: seatd project

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

seatd project seatd UPGRADE
Affected: >= 0.6.0 and < 0.6.4
Fixed in: 0.6.4
Safe to downgrade to: a release before 0.6.0
1. Check installed version
apt-cache policy seatd || rpm -q seatd || seatd --version
2. UPGRADE to 0.6.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade seatd
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade seatd
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.6.0 (Debian / Ubuntu)
apt-cache madison seatd sudo apt install seatd=<VERSION_BEFORE_0.6.0> sudo apt-mark hold seatd
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list seatd sudo dnf downgrade seatd-<VERSION_BEFORE_0.6.0> sudo dnf versionlock add seatd
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-2022-25643?

seatd: upgrade to 0.6.4. Exact commands for each OS are on this page.

Is CVE-2022-25643 being exploited?

CVE-2022-25643 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-2022-25643 affect?

CVE-2022-25643 affects seatd. Severity is critical (CVSS 9.8). seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.

How urgent is CVE-2022-25643?

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

Related CVEs

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.