CVE-2026-103110

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

GHSA-4qcw-c3r4-gc9h ↗EUVD-2026-89587 ↗

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
CWE-787 Out-of-bounds Write
ETK-2026-76, permanent identifier
19d 19h 49msince last run
1h 04mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+30h55m
0
+2h
+4h
+6h
+8h
+10h

description

Pexip Infinity Conferencing Nodes are affected by improper input validation in releases before 38.2 and in 39.0, 39.1, and 40.0. An attacker able to reach an affected node remotely may execute code as an unprivileged user.

mitigation

Upgrade Pexip Infinity to version 38.2.0. Restrict remote access to Conferencing Nodes until the update is deployed.

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.61%48th percentile
agent run time
1h 04m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 03:03Z
Δ 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 03:03Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-76",
  "cve_id": "CVE-2026-103110",
  "display_id": "CVE-2026-103110",
  "ghsa_id": "GHSA-4qcw-c3r4-gc9h",
  "euvd_id": "EUVD-2026-89587",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper input validation in Pexip Infinity",
  "summary": "Pexip Infinity Conferencing Nodes are affected by improper input validation in releases before 38.2 and in 39.0, 39.1, and 40.0. An attacker able to reach an affected node remotely may execute code as an unprivileged user.",
  "mitigation": "Upgrade Pexip Infinity to version 38.2.0. Restrict remote access to Conferencing Nodes until the update is deployed.",
  "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": [
    787
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0061,
  "epss_percentile": 0.4815,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 63.56206435,
  "t0_at": "2026-09-30T03:03:07.449000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T03:03:07.449000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T03:03:07.449000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103110"
    }
  }
}

published 2026-09-30 04:00Z
last change 2026-10-21 02:54Z

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.