# CVE-2026-95271: dgtlmoon changedetection.io Authentication Hook flask_app.py check_authentication improper authentication

> Remote attackers can bypass authentication in changedetection.io due to improper checks in the authentication hook, potentially gaining unauthorized access.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-3xg4-jrjp-f8g4

## What is CVE-2026-95271?

CVE-2026-95271 is a medium-severity authentication bypass vulnerability in dgtlmoon changedetection.io, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in dgtlmoon changedetection.io up to 0.60.7. The impacted element is the function check_authentication of the file changedetectionio/flask_app.py of the component Authentication Hook. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-95271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95271 is a medium-severity authentication bypass vulnerability in dgtlmoon changedetection.io, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95271 exists.

Affected product: dgtlmoon changedetection.io. 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-2026-95271/ (Markdown: https://insights.sbomify.com/CVE-2026-95271/index.md)
```

## Sources

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

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