{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107314 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-107314 is a medium-severity vulnerability in pgjdbc, published on 7 Oct 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-107314 and fix it if it is affected.\n\nWhat it is: CVE-2026-107314 is a medium-severity vulnerability in pgjdbc, published on 7 Oct 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-107314 in the wild and no public exploit code.\n\nAffected product: pgjdbc. 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-107314/ (Markdown: https://insights.sbomify.com/CVE-2026-107314/index.md)","id":"CVE-2026-107314","markdown":"https://insights.sbomify.com/CVE-2026-107314/index.md","name":"CVE-2026-107314","record":{"aliases":["CLEANSTART-2026-WS83724","DEBIAN-CVE-2026-107314","GHSA-rhp9-mr79-r74h","UBUNTU-CVE-2026-107314"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL JDBC Driver","requires_auth":"none","summary":"Misconfigured requireAuth settings in pgjdbc allow attackers to bypass authentication restrictions and capture cleartext database passwords via man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PostgreSQL","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"}],"description":"pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.11 through 42.7.13 enforce no restriction when the requireAuth connection property excludes all six authentication methods the driver knows, for example requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none. The driver then accepts any method the server asks for, including cleartext password authentication. A value without a method in it, such as requireAuth=, (a single comma), is affected the same way. An attacker positioned between the application and its server can ask for cleartext password authentication and receive the database password. A positive list such as requireAuth=scram-sha-256, and a partial exclusion such as requireAuth=!password,!md5, are enforced correctly. The property has no default value, so a deployment that does not set it is not affected. 42.7.14 fixes the problem: such a connection is refused with SQLState 08004, and a value without a method in it is rejected as invalid.","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":"pgjdbc does not enforce requireAuth when the value excludes every authentication method","id":"CVE-2026-107314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"pgjdbc pads a value shorter than its declared length with bytes of earlier statements (rather than zeros)","id":"CVE-2026-107315"},"packages":[],"prev":{"headline":"pgjdbc stores bytes of earlier messages in place of a large value on GSS-encrypted connections","id":"CVE-2026-107313"},"products":["pgjdbc"],"published":"2026-10-07","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-10-08","vendors":["pgjdbc"]},"summary":"Misconfigured requireAuth settings in pgjdbc allow attackers to bypass authentication restrictions and capture cleartext database passwords via man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2026-107314/"}