How severe is CVE-2026-41895?

No CVSS score has been assigned to CVE-2026-41895 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-41895?

CVE-2026-41895 affects the following packages: changedetection-io (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-41895?

No patched version of changedetection-io has shipped for CVE-2026-41895 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2026-41895 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for changedetection-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-41895 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-41895?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-41895 can be triaged on real exposure rather than presence alone.

Is CVE-2026-41895 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41895 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-41895?

CVE-2026-41895 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-41895?

CVE-2026-41895 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-41895 published, and has it been updated?

CVE-2026-41895 was published on May 12, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-41895 — changedetection-io

CVE-2026-41895 is a XML External Entity (XXE) vulnerability in changedetection-io. No vendor fix is recorded yet; mitigation options are listed below.

changedetection.io: XXE vulnerability in the changedetection.io project

Also known asGHSA-v7cp-2cx9-x793PYSEC-2026-29

Published

May 12, 2026

Updated

Aug 12, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41895.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍changedetection-io

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

changedetection.io_XXE_01 Vulnerability Report: We discovered a XXE vulnerability in the changedetection.io project

While analyzing the code logic, it was determined that an area may lead to unintended behavior under specific conditions. With the project's security in mind, see the analysis results to discern whether this may indicate a potential security risk.

Overview

SOURCE_VERSION: 0.54.9 (9f3a9fdc18bba404244801e5df8109e213ce9ff4)
Vulnerability type: XXE
Finding title: XML XPath helpers parse untrusted XML with entity resolution left to lxml defaults
Affected location: changedetectionio/html_tools.py:287

Root Cause

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(...).

Source-to-Sink Chain

Untrusted XML/RSS response content is fetched from monitored URLs.
Stream detection marks the content as XML/RSS and the include-filter path invokes xpath_filter(..., is_xml=True).
xpath_filter() builds the default XML parser and calls etree.fromstring(...) at changedetectionio/html_tools.py:287.
External entity declarations in attacker XML can be expanded by parser-default behavior in affected runtime combinations.

Exploitation Preconditions

Attacker controls the watched XML/RSS response body.
The watch uses an XPath include filter that triggers XML helper parsing.
Runtime parser behavior allows external entity expansion (for example, vulnerable dependency/default combinations).
The process can read the referenced local resource.

Risk

The XML helper path can turn watch processing into a local file disclosure primitive when entity expansion is enabled by parser defaults.

Impact

Sensitive local files can be exposed into extracted watch output, diff history, and downstream notification channels.

Remediation

Harden XML parser construction with resolve_entities=False, load_dtd=False, and no_network=True.
Reject DOCTYPE/entity declarations for untrusted XML if DTD features are unnecessary.
Add regression tests that assert external entities are never expanded in XPath XML helper flows.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`changedetection-io`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for changedetection-io, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of changedetection-io has shipped for CVE-2026-41895 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-41895 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-41895. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# changedetection.io_XXE_01 Vulnerability Report: We discovered a XXE vulnerability in the changedetection.io project While analyzing the code logic, it was determined that an area may lead to unintended behavior under specific conditions. With the project's security in mind, see the analysis results to discern whether this may indicate a potential security risk. ## Overview - SOURCE_VERSION: `0.54.9 (9f3a9fdc18bba404244801e5df8109e213ce9ff4)` - Vulnerability type: `XXE` - Finding title: `XML XPath helpers parse untrusted XML with entity resolution left to lxml defaults` - Affected location:

O3 Security · Impact-Aware SCA

Is CVE-2026-41895 in your dependencies?

O3 Security finds CVE-2026-41895 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works