CVE-2026-116238

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

GHSA-jq9v-4fgp-83ww ↗EUVD-2026-114379 ↗

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.
pgadmin.org pgAdmin 4 < 9.19
fixed in 9.19
CWE-307 Improper Restriction of Excessive Authentication Attempts
ETK-2026-3112Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 05msince last run
38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h36m
0
+4h
+6h
+8h
+10h
+12h

description

pgAdmin 4 server-mode deployments before 9.19 may fail to apply configured login-attempt limits to internal accounts. An unauthenticated attacker could make repeated password guesses when affected authentication paths are reachable; desktop-mode installations are not affected.

mitigation

Upgrade pgAdmin 4 to version 9.19 or later. Until upgraded, restrict access to the server-mode login interface to trusted networks and users.

fixed in 9.19

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.
–
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 19:55Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-30 19:55Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3112",
  "cve_id": "CVE-2026-116238",
  "display_id": "CVE-2026-116238",
  "ghsa_id": "GHSA-jq9v-4fgp-83ww",
  "euvd_id": "EUVD-2026-114379",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Login lockout bypass in pgAdmin 4 server mode",
  "summary": "pgAdmin 4 server-mode deployments before 9.19 may fail to apply configured login-attempt limits to internal accounts. An unauthenticated attacker could make repeated password guesses when affected authentication paths are reachable; desktop-mode installations are not affected.",
  "mitigation": "Upgrade pgAdmin 4 to version 9.19 or later. Until upgraded, restrict access to the server-mode login interface to trusted networks and users.",
  "vendor": "pgadmin.org",
  "product": "pgAdmin 4",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 9.19"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.19"
      ],
      "package_name": "pgAdmin 4",
      "purl": null
    }
  ],
  "cwes": [
    307
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.36127831666667,
  "t0_at": "2026-10-30T19:55:11.056000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T19:55:11.056000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T19:55:11.056000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116238"
    }
  }
}

published 2026-10-30 20:52Z
last change 2026-10-30 22:10Z

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.