# CVE-2026-33981: Changedetection.io Discloses Environment Variables via jq env Builtin in Include Filters

> An attacker can leak sensitive environment variables via jq include filters in changedetection.io, exposing secrets like passwords and proxy URLs.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-58r7-4wr5-hfx8, PYSEC-2026-2130

## What is CVE-2026-33981?

CVE-2026-33981 is a high-severity vulnerability in dgtlmoon changedetection.io, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

changedetection.io is a free open source web page change detection tool. Prior to 0.54.7, the `jq:` and `jqraw:` include filter expressions allow use of the jq `env` builtin, which reads all process environment variables and stores them as the watch snapshot. An authenticated user (or unauthenticated user when no password is set, the default) can leak sensitive environment variables including `SALTED_PASS`, `PLAYWRIGHT_DRIVER_URL`, `HTTP_PROXY`, and any secrets passed as env vars to the container. Version 0.54.7 patches the issue.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-33981?

3 open source packages ship an affected version, including changedetection.io and changedetection-io. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `changedetection.io` | PyPI | All versions | 0.54.7 |
| `changedetection-io` | PyPI | All versions | 0.54.7 |
| `changedetection-io` | PyPI | All versions | 0.54.7 |

Products: Webtechnologies Changedetection.

## How do I fix CVE-2026-33981?

Upgrade changedetection.io to 0.54.7 or later.

## Is CVE-2026-33981 being exploited?

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

## Other vulnerabilities in dgtlmoon changedetection.io

- [CVE-2026-35490](https://insights.sbomify.com/CVE-2026-35490/): changedetection.io has an Authentication Bypass via Decorator Ordering (critical 9.8)
- [CVE-2026-29039](https://insights.sbomify.com/CVE-2026-29039/): changedetection.io: XPath - Arbitrary File Read via unparsed-text() (high 8.8)
- [CVE-2026-29065](https://insights.sbomify.com/CVE-2026-29065/): changedetection.io: Zip Slip vulnerability in the backup restore functionality (high 8.8)
- [CVE-2026-27696](https://insights.sbomify.com/CVE-2026-27696/): changedetection.io Vulnerable to Server-Side Request Forgery (SSRF) via Watch URLs (high 8.6)
- [CVE-2026-41895](https://insights.sbomify.com/CVE-2026-41895/): changedetection.io: XXE vulnerability in the changedetection.io project (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33981 and fix it if it is affected.

What it is: CVE-2026-33981 is a high-severity vulnerability in dgtlmoon changedetection.io, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33981 exists.

Affected packages and fixed versions:
- changedetection.io (PyPI): affected all versions; fixed in 0.54.7
- changedetection-io (PyPI): affected all versions; fixed in 0.54.7
- changedetection-io (PyPI): affected all versions; fixed in 0.54.7

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-2026-33981/ (Markdown: https://insights.sbomify.com/CVE-2026-33981/index.md)
```

## Sources

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

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