CVE-2026-107349

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

GHSA-h8cj-p2h5-hm79 ↗EUVD-2026-101499 ↗

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.
PgBouncer >= 1.20.0, < 1.26.1
fixed in 1.26.1
ETK-2026-1872Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 02h 37msince last run
50mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+66h27m
0
+2h
+4h
+6h
+8h
+10h

description

PgBouncer versions 1.20.0 through 1.26.0 can enter a CPU-consuming loop while processing a client startup request, leaving the single PgBouncer process unable to serve clients. An attacker only needs network access to a PgBouncer listener that accepts unauthenticated connections.

mitigation

Upgrade PgBouncer to version 1.26.1 or later. Until upgrading, restrict network access to PgBouncer listeners to trusted clients.

fixed in 1.26.1

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.
–
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.42%35th percentile
agent run time
50m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 17:34Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 17:34Z
    ghsa: trigger signal, started the run
  2. 2026-10-14 17:34Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1872",
  "cve_id": "CVE-2026-107349",
  "display_id": "CVE-2026-107349",
  "ghsa_id": "GHSA-h8cj-p2h5-hm79",
  "euvd_id": "EUVD-2026-101499",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated infinite-loop denial of service in PgBouncer",
  "summary": "PgBouncer versions 1.20.0 through 1.26.0 can enter a CPU-consuming loop while processing a client startup request, leaving the single PgBouncer process unable to serve clients. An attacker only needs network access to a PgBouncer listener that accepts unauthenticated connections.",
  "mitigation": "Upgrade PgBouncer to version 1.26.1 or later. Until upgrading, restrict network access to PgBouncer listeners to trusted clients.",
  "vendor": null,
  "product": "PgBouncer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.20.0, < 1.26.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.26.1"
      ],
      "package_name": "PgBouncer",
      "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.0042,
  "epss_percentile": 0.3513,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 50.46667535,
  "t0_at": "2026-10-14T17:34:33.785000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T17:34:33.785000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T17:34:33.785000+00:00",
      "url": "https://github.com/advisories/GHSA-h8cj-p2h5-hm79"
    }
  }
}

published 2026-10-17 11:11Z
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.