{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126611 in the wild and no public exploit code.","exposure":"Only installations with a non-default setting turned on are exposed.","fix":"No fix has been published for CVE-2026-126611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126611 is a high-severity security feature bypass vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-126611 and fix it if it is affected.\n\nWhat it is: CVE-2026-126611 is a high-severity security feature bypass vulnerability in Progressive Robot Ltd hMailServer, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-126611 in the wild and no public exploit code.\nExposure: Only installations with a non-default setting turned on are exposed.\n\nAffected product: Progressive Robot Ltd hMailServer. 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-126611/ (Markdown: https://insights.sbomify.com/CVE-2026-126611/index.md)","id":"CVE-2026-126611","markdown":"https://insights.sbomify.com/CVE-2026-126611/index.md","name":"CVE-2026-126611","record":{"aliases":["GHSA-pm2h-xjj9-fw84"],"analysis":{"component_type":"server_software","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"mail server","requires_auth":"low_privilege","requires_specific_call":false,"summary":"A local attacker impersonating the database server can capture hMailServer database credentials and read or modify traffic when full TLS certificate verification is used.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitLab","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database, TlsMode=verify-full and no TlsCaFile, does not verify the database server's certificate's issuer or name when the connection is one that MariaDB Connector/C treats as local - Server= set to 127.0.0.1, ::1 or localhost (on Linux a Unix socket), to . on Windows (a named pipe), or to a comma-separated list of servers that holds such an element - which allows a local attacker who can stand in for the database server, for example by listening on its port while it is stopped or restarting, to receive the database sign-in, the password included, and to read and modify the traffic between hMailServer and its database. hMailServer applied verify-full by turning the client's certificate verification on without a CA file, but MariaDB Connector/C 3.4.1 and later, on a connection they treat as local and with no CA file, accept any certificate within its validity period that is self-signed or sent with its own root, for any name (Connector/C 3.4.2 to 3.4.10 also one whose issuer they cannot find), so the client accepted the certificate an impostor made, asked no proof of the password and allowed a switch to an authentication method that sends the password unhashed, while hmailserver --check-database said the certificate had been checked against the system's trust store and the application log that it had been checked. The Windows builds bundle Connector/C 3.4.9 (6.3.4 to 6.3.6) and 3.4.11 (6.3.7); on Linux the distribution's client is used, and Connector/C 3.3 and 3.4.0 and Oracle's MySQL client are not affected. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Certificate Validation in hMailServer","id":"CVE-2026-126611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Link Resolution Before File Access ('Link Following') in hMailServer","id":"CVE-2026-126612"},"nickname":null,"packages":[],"prev":{"headline":"Improper Certificate Validation in hMailServer","id":"CVE-2026-126610"},"products":["hMailServer"],"published":"2026-11-11","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-11","vendors":["Progressive Robot Ltd"]},"summary":"A local attacker impersonating the database server can capture hMailServer database credentials and read or modify traffic when full TLS certificate verification is used.","url":"https://insights.sbomify.com/CVE-2026-126611/"}