CVE-2026-116322

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

GHSA-j4qg-6655-x9r7 ↗EUVD-2026-124502 ↗

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.
PostgreSQL >= 18, < 18.7
fixed in 18.7
ETK-2026-4680Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 05h 46msince last run
1h 00mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+121h52m
0
+2h
+4h
+6h
+8h
+10h

description

PostgreSQL 18 releases before 18.7 are affected by an improper-locking issue in startup processing. An unauthenticated network client may trigger a server restart, resulting in a denial of service. The attacker must be able to reach the PostgreSQL service over the network.

mitigation

Upgrade PostgreSQL 18 to version 18.7 or later. Restrict network access to the database service to reduce exposure until upgrading.

fixed in 18.7

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.37%30th percentile
agent run time
1h 00m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 14:15Z
Δ 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-11-12 14:15Z
  2. 2026-11-12 14:15Z
  3. 2026-11-17 13:26Z
    PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE

this entry in the feed

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

{
  "etk_id": "ETK-2026-4680",
  "cve_id": "CVE-2026-116322",
  "display_id": "CVE-2026-116322",
  "ghsa_id": "GHSA-j4qg-6655-x9r7",
  "euvd_id": "EUVD-2026-124502",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper locking allows PostgreSQL server restart",
  "summary": "PostgreSQL 18 releases before 18.7 are affected by an improper-locking issue in startup processing. An unauthenticated network client may trigger a server restart, resulting in a denial of service. The attacker must be able to reach the PostgreSQL service over the network.",
  "mitigation": "Upgrade PostgreSQL 18 to version 18.7 or later. Restrict network access to the database service to reduce exposure until upgrading.",
  "vendor": null,
  "product": "PostgreSQL",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 18, < 18.7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "18.7"
      ],
      "package_name": "PostgreSQL",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 5.3,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
  "epss_score": 0.0037,
  "epss_percentile": 0.3093,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 59.620167816666665,
  "t0_at": "2026-11-12T14:15:12.887000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T14:15:12.887000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T14:15:12.887000+00:00",
      "url": "https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html"
    }
  }
}

published 2026-11-17 15:07Z
last change 2026-11-18 21:09Z

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.