CVE-2026-56851

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

GHSA-gx9w-9qq8-m485 ↗EUVD-2026-94532 ↗

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.
golang.org/x/text golang.org/x/text/secure/precis < 0.41.0
fixed in 0.41.0
CWE-787 Out-of-bounds Write
ETK-2026-1334Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 19h 55msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+111h07m
0
+2h
+4h
+6h
+8h
+10h

description

Applications using the golang.org/x/text Nickname profile may panic while handling attacker-controlled text. An attacker must be able to cause crafted input to be transformed into a short destination buffer, potentially causing a denial of service.

mitigation

Upgrade golang.org/x/text/secure/precis to 0.41.0 or later.

fixed in 0.41.0

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.
0.34%25th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 17:46Z
Δ 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-07 17:46Z
    ghsa: trigger signal, started the run
  2. 2026-10-07 17:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1334",
  "cve_id": "CVE-2026-56851",
  "display_id": "CVE-2026-56851",
  "ghsa_id": "GHSA-gx9w-9qq8-m485",
  "euvd_id": "EUVD-2026-94532",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds panic in golang.org/x/text Nickname profile",
  "summary": "Applications using the golang.org/x/text Nickname profile may panic while handling attacker-controlled text. An attacker must be able to cause crafted input to be transformed into a short destination buffer, potentially causing a denial of service.",
  "mitigation": "Upgrade golang.org/x/text/secure/precis to 0.41.0 or later.",
  "vendor": "golang.org/x/text",
  "product": "golang.org/x/text/secure/precis",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.41.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.41.0"
      ],
      "package_name": "golang.org/x/text/secure/precis",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2541,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.354054683333333,
  "t0_at": "2026-10-07T17:46:35.620000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T17:46:35.620000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T17:46:35.620000+00:00",
      "url": "https://github.com/advisories/GHSA-gx9w-9qq8-m485"
    }
  }
}

published 2026-10-12 08:40Z
last change 2026-10-21 04:45Z

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.