CVE-2026-75614

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

GHSA-825c-7h77-2jjq ↗EUVD-2026-117599 ↗

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.
esa asn1scc < 4.7.0.1
fixed in 4.7.0.1
CWE-129 Improper Validation of Array Index
ETK-2026-3650Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 20msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h39m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ASN1SCC versions before 4.7.0.1 can generate decoders that mishandle invalid constrained size values for several variable-length ASN.1 types. An attacker who can supply crafted encoded data for decoding may cause memory corruption, crashes, or possible code execution.

mitigation

Upgrade asn1scc to version 4.7.0.1 or later. Until upgraded, avoid decoding untrusted uPER or ACN data with affected generated decoders.

fixed in 4.7.0.1

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-11-05 16:47Z
Δ 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 16:47Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3650",
  "cve_id": "CVE-2026-75614",
  "display_id": "CVE-2026-75614",
  "ghsa_id": "GHSA-825c-7h77-2jjq",
  "euvd_id": "EUVD-2026-117599",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in ASN1SCC decoders",
  "summary": "ASN1SCC versions before 4.7.0.1 can generate decoders that mishandle invalid constrained size values for several variable-length ASN.1 types. An attacker who can supply crafted encoded data for decoding may cause memory corruption, crashes, or possible code execution.",
  "mitigation": "Upgrade asn1scc to version 4.7.0.1 or later. Until upgraded, avoid decoding untrusted uPER or ACN data with affected generated decoders.",
  "vendor": "esa",
  "product": "asn1scc",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 4.7.0.1"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "4.7.0.1"
      ],
      "package_name": "asn1crt",
      "purl": null
    }
  ],
  "cwes": [
    129
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.6923579,
  "t0_at": "2026-11-05T16:47:56.986000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T16:47:56.986000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T16:47:56.986000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-75614"
    }
  }
}

published 2026-11-05 17:15Z
last change 2026-11-05 18:56Z

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.