{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92871 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-92871 is a high-severity vulnerability in Pgpool-II, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92871 and fix it if it is affected.\n\nWhat it is: CVE-2026-92871 is a high-severity vulnerability in Pgpool-II, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92871 in the wild and no public exploit code.\n\nAffected product: Pgpool-II. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92871/ (Markdown: https://insights.sbomify.com/CVE-2026-92871/index.md)","id":"CVE-2026-92871","markdown":"https://insights.sbomify.com/CVE-2026-92871/index.md","name":"CVE-2026-92871","record":{"aliases":["DEBIAN-CVE-2026-92871","GHSA-98gg-48ph-mg6c"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Pgpool-II connection pooler","requires_auth":"none","summary":"An unauthenticated attacker can cause a denial of service by triggering a NULL pointer dereference in the Pgpool-II watchdog process.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A NULL pointer dereference vulnerability exists in Pgpool-II, which may allow an unauthenticated attacker to cause abnormal termination of the watchdog process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Null dereference in Pgpool-II","id":"CVE-2026-92871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Pgpool-II","id":"CVE-2026-92872"},"packages":[],"prev":{"headline":"Memory corruption in Pgpool-II","id":"CVE-2026-92870"},"products":["Pgpool-II"],"published":"2026-09-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Pgpool Global Development Group"]},"summary":"An unauthenticated attacker can cause a denial of service by triggering a NULL pointer dereference in the Pgpool-II watchdog process.","url":"https://insights.sbomify.com/CVE-2026-92871/"}