CVE-2026-119741

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2026-115914 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
RsyncProject rsync <= 3.5.1
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-3379Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 02msince last run
42mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h05m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

rsync through 3.5.1 can be made to perform excessive checksum work while serving delta transfers. An unauthenticated remote client may exhaust sender CPU when it can pull from a publicly accessible rsync daemon module.

mitigation

Restrict rsync daemon modules to trusted clients and apply connection or rate limits to reduce CPU-exhaustion exposure. No fixed rsync release is recorded; monitor upstream for an update and deploy it when available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
42m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 15:26Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-03 15:26Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-119741

{
  "etk_id": "ETK-2026-3379",
  "cve_id": "CVE-2026-119741",
  "display_id": "CVE-2026-119741",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-115914",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CPU denial of service in rsync delta transfer",
  "summary": "rsync through 3.5.1 can be made to perform excessive checksum work while serving delta transfers. An unauthenticated remote client may exhaust sender CPU when it can pull from a publicly accessible rsync daemon module.",
  "mitigation": "Restrict rsync daemon modules to trusted clients and apply connection or rate limits to reduce CPU-exhaustion exposure. No fixed rsync release is recorded; monitor upstream for an update and deploy it when available.",
  "vendor": "RsyncProject",
  "product": "rsync",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.5.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rsync",
      "purl": null
    }
  ],
  "cwes": [
    407
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 41.73398181666666,
  "t0_at": "2026-11-03T15:26:27.533000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T15:26:27.533000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T15:26:27.533000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119741"
    }
  }
}

published 2026-11-03 15:50Z
last change 2026-11-03 17:05Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.