CVE-2026-112320

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

GHSA-hjgq-cq7f-j633 ↗EUVD-2026-120236 ↗

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.
Red Hat Enterprise Linux 10
CWE-772 Missing Release of Resource after Effective Lifetime
ETK-2026-3998Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 07h 56msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h42m
0
+2h
+6h
+8h
+10h
+12h

description

Red Hat Enterprise Linux 10 systems using the affected krb5 GSS-RPC code may allow kadmind to retain obsolete authentication contexts. An unauthenticated remote client that can reach kadmind may exhaust service memory by repeatedly changing authentication types on a persistent TCP connection.

mitigation

Restrict network access to kadmind to trusted administrative hosts and networks until a vendor update is available. Monitor kadmind memory use and restart the service if resource consumption becomes excessive.

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
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 19:08Z
Δ 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-09 19:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3998",
  "cve_id": "CVE-2026-112320",
  "display_id": "CVE-2026-112320",
  "ghsa_id": "GHSA-hjgq-cq7f-j633",
  "euvd_id": "EUVD-2026-120236",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication-context memory leak in krb5 GSS-RPC",
  "summary": "Red Hat Enterprise Linux 10 systems using the affected krb5 GSS-RPC code may allow kadmind to retain obsolete authentication contexts. An unauthenticated remote client that can reach kadmind may exhaust service memory by repeatedly changing authentication types on a persistent TCP connection.",
  "mitigation": "Restrict network access to kadmind to trusted administrative hosts and networks until a vendor update is available. Monitor kadmind memory use and restart the service if resource consumption becomes excessive.",
  "vendor": "Red Hat",
  "product": "Red Hat Enterprise Linux 10",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "krb5",
      "purl": null
    }
  ],
  "cwes": [
    772
  ],
  "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": 36.1823852,
  "t0_at": "2026-11-09T19:08:07.434000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T19:08:07.434000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T19:08:07.434000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112320"
    }
  }
}

published 2026-11-09 22:14Z
last change 2026-11-11 05:12Z

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.