CVE-2026-122146

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

GHSA-3xf2-c6c2-98qc ↗EUVD-2026-117202 ↗

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.
101arrowz fflate 0.8.0; 0.8.1; 0.8.2; 0.8.3
ETK-2026-3577Zero's internal tracking ID, independent of the CVE number., permanent identifier
18h 39msince last run
4mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h26m
0
+2h
+6h
+8h
+10h
+12h

description

fflate versions through 0.8.3 are affected by a memory-corruption issue in the synchronous ZIP extraction path. An unauthenticated remote attacker may trigger the issue if an application passes attacker-controlled ZIP data to the affected function.

mitigation

Do not pass untrusted ZIP data to fflate's synchronous extraction function, and isolate or reject such inputs where possible. No fixed version is established by the available evidence; monitor upstream for a patched release and upgrade promptly.

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
4m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 00:45Z
Δ 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-05 00:45Z
    ghsa: trigger signal, started the run
  2. 2026-11-05 00:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3577",
  "cve_id": "CVE-2026-122146",
  "display_id": "CVE-2026-122146",
  "ghsa_id": "GHSA-3xf2-c6c2-98qc",
  "euvd_id": "EUVD-2026-117202",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory corruption in fflate ZIP extraction",
  "summary": "fflate versions through 0.8.3 are affected by a memory-corruption issue in the synchronous ZIP extraction path. An unauthenticated remote attacker may trigger the issue if an application passes attacker-controlled ZIP data to the affected function.",
  "mitigation": "Do not pass untrusted ZIP data to fflate's synchronous extraction function, and isolate or reject such inputs where possible. No fixed version is established by the available evidence; monitor upstream for a patched release and upgrade promptly.",
  "vendor": "101arrowz",
  "product": "fflate",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "0.8.0",
        "0.8.1",
        "0.8.2",
        "0.8.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "fflate",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 4.031865233333333,
  "t0_at": "2026-11-05T00:45:26.038000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T00:45:26.038000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T00:45:26.038000+00:00",
      "url": "https://github.com/advisories/GHSA-3xf2-c6c2-98qc"
    }
  }
}

published 2026-11-05 04:07Z
last change 2026-11-05 09: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.