# CVE-2022-31149: ActivityWatch vulnerable to DNS rebinding attack

> Attackers can bypass origin checks via DNS rebinding to access the ActivityWatch REST API, exposing user activity data.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-v9fg-6g9j-h4x4

## What is CVE-2022-31149?

CVE-2022-31149 is a high-severity vulnerability in activitywatch, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2022-31149?

It affects 1 product.


Products: Activitywatch Activitywatch.

## How do I fix CVE-2022-31149?

No fix has been published for CVE-2022-31149 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-31149 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31149 exists.

## Other vulnerabilities in activitywatch

- [CVE-2021-32692](https://insights.sbomify.com/CVE-2021-32692/): Activity Watch vulnerable to command execution on macOS via printAppTitle.scpt (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31149 and fix it if it is affected.

What it is: CVE-2022-31149 is a high-severity vulnerability in activitywatch, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31149 exists.

Affected product: activitywatch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31149/ (Markdown: https://insights.sbomify.com/CVE-2022-31149/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31149
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31149
- OSV: https://osv.dev/vulnerability/CVE-2022-31149

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31149/
Summaries are generated and may contain mistakes; the official description above is the record.