CVE-2026-76077

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

GHSA-38q3-fg5h-wwf9 ↗EUVD-2026-117601 ↗

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-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
ETK-2026-3651Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 24msince 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+0h37m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ASN1SCC releases before 4.7.0.1 contain memory-safety flaws in the runtime XER decoder. An attacker who can supply malformed XER data to an application that decodes it may cause crashes or hangs, expose memory, corrupt process state, or potentially execute code.

mitigation

Upgrade asn1scc to version 4.7.0.1 or later. Until upgrades are complete, prevent untrusted XER data from reaching ASN1SCC decode paths.

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:49Z
Δ 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:49Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3651",
  "cve_id": "CVE-2026-76077",
  "display_id": "CVE-2026-76077",
  "ghsa_id": "GHSA-38q3-fg5h-wwf9",
  "euvd_id": "EUVD-2026-117601",
  "status": "published",
  "anchor_state": "anchored",
  "title": "XER decoder memory-safety flaws in asn1scc",
  "summary": "ASN1SCC releases before 4.7.0.1 contain memory-safety flaws in the runtime XER decoder. An attacker who can supply malformed XER data to an application that decodes it may cause crashes or hangs, expose memory, corrupt process state, or potentially execute code.",
  "mitigation": "Upgrade asn1scc to version 4.7.0.1 or later. Until upgrades are complete, prevent untrusted XER data from reaching ASN1SCC decode paths.",
  "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": [
    120
  ],
  "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": 11.441834366666667,
  "t0_at": "2026-11-05T16:49:58.765000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T16:49:58.765000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T16:49:58.765000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76077"
    }
  }
}

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.