CVE-2026-103109

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

GHSA-584g-7p7q-99pg ↗EUVD-2026-89585 ↗

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.
Pexip Infinity < 38.2.0; 39.0.0; 39.1.0; 40.0.0
fixed in 38.2.0
ETK-2026-77, permanent identifier
20d 01h 00msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+26h44m
0
+2h
+4h
+6h
+8h
+10h

description

Pexip Infinity media processing is affected in releases before 38.2 and in 39.0, 39.1, and 40.0. A remote attacker able to have a crafted media stream processed may cause an abort and denial of service, with possible memory corruption.

mitigation

Update the Infinity package to version 38.2.0, the fixed release identified in the structured advisory data. Until updates are applied, limit processing of media streams from untrusted remote sources where operationally feasible.

fixed in 38.2.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.25%15th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 02:59Z
Δ 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-09-30 02:59Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 02:59Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-77",
  "cve_id": "CVE-2026-103109",
  "display_id": "CVE-2026-103109",
  "ghsa_id": "GHSA-584g-7p7q-99pg",
  "euvd_id": "EUVD-2026-89585",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper media-stream validation in Pexip Infinity",
  "summary": "Pexip Infinity media processing is affected in releases before 38.2 and in 39.0, 39.1, and 40.0. A remote attacker able to have a crafted media stream processed may cause an abort and denial of service, with possible memory corruption.",
  "mitigation": "Update the Infinity package to version 38.2.0, the fixed release identified in the structured advisory data. Until updates are applied, limit processing of media streams from untrusted remote sources where operationally feasible.",
  "vendor": "Pexip",
  "product": "Infinity",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 38.2.0",
        "39.0.0",
        "39.1.0",
        "40.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "38.2.0"
      ],
      "package_name": "Infinity",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.1583,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.378281566666665,
  "t0_at": "2026-09-30T02:59:53.499000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T02:59:53.499000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T02:59:53.499000+00:00",
      "url": "https://github.com/advisories/GHSA-584g-7p7q-99pg"
    }
  }
}

published 2026-09-30 04:02Z
last change 2026-10-21 06:34Z

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.