CVE-2026-106807

validatedZero produced an exploit or a check.

GHSA-96p4-93rj-w6w5 ↗EUVD-2026-115347 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Open5GS n/a
ETK-2026-3306Zero's internal tracking ID, independent of the CVE number., permanent identifier
+20h19mTTV
53mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+20h19magent stopped
0
+6h
+12h
+18h

description

open5GS 2.8.0 is affected in PFCP transaction handling. An attacker able to reach an affected SMF or UPF with PFCP traffic can exhaust transaction-related capacity and cause the process to stop, interrupting service until it is restarted.

mitigation

Restrict PFCP endpoint access to trusted peers using network segmentation and firewall rules. Monitor affected SMF and UPF processes and restart them promptly if service is disrupted.

check
available
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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 00:00Z
Δ 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 check: a technique exists and was validated, 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-11-02 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3306",
  "cve_id": "CVE-2026-106807",
  "display_id": "CVE-2026-106807",
  "ghsa_id": "GHSA-96p4-93rj-w6w5",
  "euvd_id": "EUVD-2026-115347",
  "status": "published",
  "anchor_state": "anchored",
  "title": "PFCP resource-exhaustion denial of service in open5GS",
  "summary": "open5GS 2.8.0 is affected in PFCP transaction handling. An attacker able to reach an affected SMF or UPF with PFCP traffic can exhaust transaction-related capacity and cause the process to stop, interrupting service until it is restarted.",
  "mitigation": "Restrict PFCP endpoint access to trusted peers using network segmentation and firewall rules. Monitor affected SMF and UPF processes and restart them promptly if service is disrupted.",
  "vendor": null,
  "product": "Open5GS",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 53.198213716666665,
  "t0_at": "2026-11-02T00:00:00+00:00",
  "signals": {
    "check": {
      "at": "2026-11-02T20:18:41.040032+00:00",
      "days": 0.8463083337037037,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T00:00:00+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-02T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106807"
    }
  }
}

published 2026-11-02 19:25Z
last change 2026-11-02 22:32Z

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.