dbcve.org
ChangedetectionApplication · Webtechnologies

CVE-2026-41895

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to after 0.54.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
changedetection.io is a free open source web page change detection tool. In 0.54.9 and earlier, xpath_filter() switches to XML mode for XML/RSS content and creates etree.XMLParser(strip_cdata=False) without explicitly disabling external entity resolution, external DTD loading, or network-backed entity lookup. The helper then parses untrusted XML bytes directly with etree.fromstring(...).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The xpath_filter() function in changedetection.io versions 0.54.9 and earlier uses lxml's etree.XMLParser to process XML/RSS content without disabling external entity resolution, creating an XML External Entity (XXE) vulnerability. The parser loads untrusted XML directly without restricting external DTD loading or network-backed entity lookups.

MitigationConfigure XMLParser with resolve_entities=False, no_network=False (or restrict network access), and disable external DTD loading to prevent XXE attacks when processing untrusted XML/RSS content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChangedetectionApplication
Affected:<= 0.54.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify changedetection.io installation
    Locate the changedetection.io application - check for running Docker container, pip package, or source installation. Note the installation path.
    Affected if The application is present and running
  2. Determine installed version
    Run 'pip show changedetection' or check version.py file in the installation directory, or inspect Docker image tag. Compare against 0.54.9.
    Affected if Version is 0.54.9 or lower
  3. Locate xpath_filter function usage
    Search source code for 'xpath_filter' function definition - look in Python source files under the changedetection installation directory.
    Affected if The xpath_filter function exists in the codebase
  4. Inspect XMLParser configuration
    Examine the xpath_filter function code for lxml.etree.XMLParser usage. Look for resolve_entities parameter setting.
    Affected if resolve_entities is not explicitly set to False, or no external entity restriction is configured
  5. Verify XML/RSS processing is active
    Check if any watch items or configured inputs are using XPath filtering on XML or RSS feeds. Look at configuration files or database for watch definitions.
    Affected if XPath filtering is configured for any XML or RSS feed source

You are affected if running changedetection.io version 0.54.9 or earlier AND the xpath_filter function processes XML/RSS content with XMLParser lacking resolve_entities=False.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.54.9
Interim mitigation

Configure XMLParser with resolve_entities=False, no_network=False (or restrict network access), and disable external DTD loading to prevent XXE attacks when processing untrusted XML/RSS content.

Recommended fix Moderate confidence

0.55.0 or later (any release higher than 0.54.9)

  1. 1. Back up your changedetection configuration and data directory before upgrading.
  2. 2. If using Docker, pull the latest image: `docker pull changedetectionio/changedetection`
  3. 3. If using pip, upgrade the package: `pip install changedetection-io --upgrade`
  4. 4. Verify the upgrade completed successfully by checking the version number in the web UI or via CLI.
  5. 5. Test that XML/RSS feed monitoring functionality still works correctly after the upgrade.
Caveat Minor release may include other changes; review release notes for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Changedetection Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41895 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data