CVE-2022-31149: ActivityWatch open-source automated time tracker

Q: How do I fix CVE-2022-31149?

activitywatch: upgrade to 0.12.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-31149 being exploited?

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

Q: What does CVE-2022-31149 affect?

CVE-2022-31149 affects activitywatch. Severity is high (CVSS 8.8). ActivityWatch open-source automated time tracker. Versions prior to 0.12.0b2 are vulnerable to DNS rebinding attacks. This vulnerability impacts everyone running ActivityWatch and gives the attacker full access to the ActivityWatch REST API

Q: How urgent is CVE-2022-31149?

Priority 53/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

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

ActivityWatch open-source automated time tracker. Versions prior to 0.12.0b2 are vulnerable to DNS rebinding attacks. This vulnerability impacts everyone running ActivityWatch and gives the attacker full access to the ActivityWatch REST API. Users should upgrade to v0.12.0b2 or later to receive a patch. As a workaround, block DNS lookups that resolve to 127.0.0.1.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.3% (top 31%)
CISA exploited list	No
Weakness	CWE-290
Published	2022-09-07
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: activitywatch

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

Am I affected?

Timeline

2022-09-07 14:15 UTCPublished CVE record published
2026-06-17 04:44 UTCUpdated Record last modified

activitywatch activitywatch UPGRADE

Affected: < 0.12.0 · 0.12.0 beta1

Fixed in: 0.12.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 0.12.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade activitywatch

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade activitywatch

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-31149?

activitywatch: upgrade to 0.12.0. Exact commands for each OS are on this page.

Is CVE-2022-31149 being exploited?

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

CVE-2022-31149 affects activitywatch. Severity is high (CVSS 8.8). ActivityWatch open-source automated time tracker. Versions prior to 0.12.0b2 are vulnerable to DNS rebinding attacks. This vulnerability impacts everyone running ActivityWatch and gives the attacker full access to the ActivityWatch REST API

How urgent is CVE-2022-31149?

Priority 53/100. High severity; Public exploit reference

Related CVEs

CVE-2021-32692 CRITICAL 9.6 UPGRADE Activity Watch is a free and open-source automated time tracker

References

← Back to latest CVEs