CVE-2026-110755

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

GHSA-chcw-qm6q-pg64 ↗EUVD-2026-103195 ↗

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.
Text-CSV_XS < 1.65
fixed in 1.65
ETK-2026-2309Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 48msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+108h39m
0
+2h
+4h
+6h
+8h
+10h

description

Text::CSV_XS versions before 1.65 can consume disproportionate CPU while parsing CSV input with carriage-return-only line endings. An attacker able to supply CSV to an application using getline with the default end-of-line configuration can cause processing delays or resource exhaustion.

mitigation

Upgrade Text::CSV_XS to version 1.65 or later. Until upgrading, reject or normalize carriage-return-only CSV input and configure CSV line-ending handling explicitly.

fixed in 1.65

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
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 22:07Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-16 22:07Z
    ghsa: trigger signal, started the run
  2. 2026-10-16 22:07Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2309",
  "cve_id": "CVE-2026-110755",
  "display_id": "CVE-2026-110755",
  "ghsa_id": "GHSA-chcw-qm6q-pg64",
  "euvd_id": "EUVD-2026-103195",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Quadratic CPU consumption in Text::CSV_XS CSV parsing",
  "summary": "Text::CSV_XS versions before 1.65 can consume disproportionate CPU while parsing CSV input with carriage-return-only line endings. An attacker able to supply CSV to an application using getline with the default end-of-line configuration can cause processing delays or resource exhaustion.",
  "mitigation": "Upgrade Text::CSV_XS to version 1.65 or later. Until upgrading, reject or normalize carriage-return-only CSV input and configure CSV line-ending handling explicitly.",
  "vendor": null,
  "product": "Text-CSV_XS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.65"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.65"
      ],
      "package_name": "Text-CSV_XS",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.539787866666666,
  "t0_at": "2026-10-16T22:07:10.643000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T22:07:10.643000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T22:07:10.643000+00:00",
      "url": "https://github.com/advisories/GHSA-chcw-qm6q-pg64"
    }
  }
}

published 2026-10-21 10:35Z
last change 2026-10-21 13:29Z

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.