CVE-2026-103108

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

GHSA-2xqf-gx7w-hfc7 ↗EUVD-2026-89584 ↗

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-81, permanent identifier
18d 19h 30msince last run
25mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+55h26m
0
+2h
+4h
+6h
+8h
+10h

description

Pexip Infinity's media implementation is affected by improper input validation in releases before 38.2 and in 39.0, 39.1, and 40.0. A remote attacker may cause the software to abort, resulting in denial of service; the advisory does not identify an authentication prerequisite.

mitigation

Upgrade Pexip Infinity to version 38.2.0. Until upgraded, restrict remote access to affected Infinity deployments to reduce exposure.

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.31%22nd percentile
agent run time
25m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 02: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: 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:49Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 02:49Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-81",
  "cve_id": "CVE-2026-103108",
  "display_id": "CVE-2026-103108",
  "ghsa_id": "GHSA-2xqf-gx7w-hfc7",
  "euvd_id": "EUVD-2026-89584",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper input validation denial of service in Pexip Infinity",
  "summary": "Pexip Infinity's media implementation is affected by improper input validation in releases before 38.2 and in 39.0, 39.1, and 40.0. A remote attacker may cause the software to abort, resulting in denial of service; the advisory does not identify an authentication prerequisite.",
  "mitigation": "Upgrade Pexip Infinity to version 38.2.0. Until upgraded, restrict remote access to affected Infinity deployments to reduce exposure.",
  "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.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": 0.0031,
  "epss_percentile": 0.2282,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.530689216666666,
  "t0_at": "2026-09-30T02:49:52.530000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T02:49:52.530000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T02:49:52.530000+00:00",
      "url": "https://github.com/advisories/GHSA-2xqf-gx7w-hfc7"
    }
  }
}

published 2026-09-30 05:29Z
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.