dbcve.org
CWE-290Weakness · CWE-290

CVE-2026-44183

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Cleanuparr is a tool for automating the cleanup of unwanted or blocked files in Sonarr, Radarr, and supported download clients like qBittorrent. Prior to 2.9.10, TrustedNetworkAuthenticationHandler.ResolveClientIp parses the leftmost entry of the X-Forwarded-For header as the client IP. That entry is attacker-controlled — X-Forwarded-For is append-only, so the leftmost value is whatever the original HTTP client claimed. By sending a spoofed local IP in the header, an unauthenticated remote attacker passes the trusted-network check and is logged in as the Cleanuparr administrator. This vulnerability is fixed in 2.9.10.

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

Cleanuparr versions before 2.9.10 have a critical authentication bypass in TrustedNetworkAuthenticationHandler.ResolveClientIp. The function incorrectly trusts the leftmost entry of the X-Forwarded-For header as the client IP, but this value is attacker-controlled since X-Forwarded-For is append-only. Attackers can spoof a local IP address in this header to bypass the trusted-network check and gain administrator access without credentials.

MitigationUpgrade Cleanuparr to version 2.9.10 or later. Until then, consider disabling the application or restricting network access at the perimeter firewall to prevent external attackers from sending crafted requests.

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

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
High
Availability
High

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

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. Confirm Cleanuparr is installed
    Locate the Cleanuparr application on the system by searching for the executable or checking running processes and services
    Affected if Cleanuparr is found running as a process or installed service on the system
  2. Check installed version
    Run Cleanuparr with a version flag (such as --version or -v) or inspect the binary file properties to retrieve the version number, then compare it to the affected range (versions before 2.9.10)
    Affected if The installed version is lower than 2.9.10
  3. Verify TrustedNetworkAuthentication is enabled
    Inspect the Cleanuparr configuration file or settings for the TrustedNetworkAuthenticationHandler module and confirm it is actively used for authentication
    Affected if TrustedNetworkAuthentication is enabled in the configuration
  4. Assess network exposure
    Review network configuration, firewall rules, or reverse proxy settings to determine if Cleanuparr is accessible from untrusted networks where external attackers could send crafted requests with arbitrary X-Forwarded-For headers
    Affected if The application is exposed to untrusted or external networks without proper header validation

You are affected if Cleanuparr versions before 2.9.10 are running with TrustedNetworkAuthentication enabled and the service is reachable from networks where attackers can manipulate the X-Forwarded-For header to spoof trusted IP addresses.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cleanuparr to version 2.9.10 or later. Until then, consider disabling the application or restricting network access at the perimeter firewall to prevent external attackers from sending crafted requests.

Recommended fix High confidence

2.9.10

  1. Back up your Cleanuparr configuration and any relevant data
  2. Stop the Cleanuparr service
  3. Upgrade Cleanuparr to version 2.9.10 or later
  4. Verify the upgrade was successful by checking the installed version
  5. Restart the Cleanuparr service
  6. Confirm the X-Forwarded-For header handling is now correct by testing with spoofed headers

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44183 — 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-44183 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