CVE-2026-77100

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

GHSA-83mj-r2gx-wf57 ↗EUVD-2026-98762 ↗

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.
Commvault Cloud >= 11.46.0, <= 11.46.29; >= 11.44.0, <= 11.44.24; >= 11.40.0, <= 11.40.77; >= 11.36.0, <= 11.36.126
ETK-2026-1541Zero's internal tracking ID, independent of the CVE number., permanent identifier
5d 11h 44msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+69h25m
0
+2h
+4h
+6h
+8h
+10h

description

Commvault MediaAgent is affected by a heap-based buffer overflow that can disrupt service availability. The advisory does not state the preconditions required for an attacker to trigger the issue.

mitigation

Upgrade MediaAgent and HyperScale installations to the vendor's resolved maintenance release. Consult Commvault support or release documentation for the applicable maintenance version.

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.32%23rd percentile
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 14:27Z
Δ 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-13 14:27Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1541",
  "cve_id": "CVE-2026-77100",
  "display_id": "CVE-2026-77100",
  "ghsa_id": "GHSA-83mj-r2gx-wf57",
  "euvd_id": "EUVD-2026-98762",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap-based buffer overflow in Commvault MediaAgent",
  "summary": "Commvault MediaAgent is affected by a heap-based buffer overflow that can disrupt service availability. The advisory does not state the preconditions required for an attacker to trigger the issue.",
  "mitigation": "Upgrade MediaAgent and HyperScale installations to the vendor's resolved maintenance release. Consult Commvault support or release documentation for the applicable maintenance version.",
  "vendor": "Commvault",
  "product": "Commvault Cloud",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.46.0, <= 11.46.29",
        ">= 11.44.0, <= 11.44.24",
        ">= 11.40.0, <= 11.40.77",
        ">= 11.36.0, <= 11.36.126"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Commvault Cloud",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0032,
  "epss_percentile": 0.2328,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.17438908333333,
  "t0_at": "2026-10-13T14:27:01.168000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T14:27:01.168000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T14:27:01.168000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-77100"
    }
  }
}

published 2026-10-14 06:11Z
last change 2026-10-21 23:09Z

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.