{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92872 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92872 is a medium-severity vulnerability in Pgpool-II, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92872 and fix it if it is affected.\n\nWhat it is: CVE-2026-92872 is a medium-severity vulnerability in Pgpool-II, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92872 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-92872/ (Markdown: https://insights.sbomify.com/CVE-2026-92872/index.md)","id":"CVE-2026-92872","markdown":"https://insights.sbomify.com/CVE-2026-92872/index.md","name":"CVE-2026-92872","record":{"aliases":["DEBIAN-CVE-2026-92872","GHSA-84mj-xfmv-f82h"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pgpool-II connection pooler","requires_auth":"low_privilege","summary":"An authenticated attacker can obtain sensitive cluster information from Pgpool-II log files, potentially aiding further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Pgpool-II inserts sensitive information into log file, which may allow an authenticated attacker to obtain the cluster information.","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":"Information disclosure in Pgpool-II","id":"CVE-2026-92872","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in Pgpool-II","id":"CVE-2026-92873"},"packages":[],"prev":{"headline":"Null dereference in Pgpool-II","id":"CVE-2026-92871"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["Pgpool Global Development Group"]},"summary":"An authenticated attacker can obtain sensitive cluster information from Pgpool-II log files, potentially aiding further attacks.","url":"https://insights.sbomify.com/CVE-2026-92872/"}