{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105031 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105031 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105031 and fix it if it is affected.\n\nWhat it is: CVE-2026-105031 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105031 in the wild and no public exploit code.\n\nAffected product: Apache Qpid Proton C. 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-105031/ (Markdown: https://insights.sbomify.com/CVE-2026-105031/index.md)","id":"CVE-2026-105031","markdown":"https://insights.sbomify.com/CVE-2026-105031/index.md","name":"CVE-2026-105031","record":{"aliases":["DEBIAN-CVE-2026-105031","GHSA-75pq-3xrq-9pc6"],"analysis":null,"analysis_generated_by":null,"assigner":"apache","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() \u0026 pn_tls_config_set_trusted_certs() APIs added to rather than replaced the default system trust anchors. Leading to potentially trusting unexpected peer certificates.\n\nThis can be worked around by setting the SSL_CERT_FILE environment variable for the application to /dev/null.\n\nThis issue does not affect the Win32 SChannel TLS implementation.\n\nThis issue affects Apache Qpid Proton C: through 0.40.0.\n\nUsers are recommended to upgrade to version 0.41.1, which fixes the issue.","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":"When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() \u0026 pn_tls_config_set_trusted_certs() APIs added to rath","id":"CVE-2026-105031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"EnergizeLab Eilik AI Skill Upload Unauthenticated Path Traversal Arbitrary File Write","id":"CVE-2026-105032"},"packages":[],"prev":{"headline":"Kener 4.0.0 before 4.1.6 Hidden Monitor Data Disclosure via Dashboard API","id":"CVE-2026-105030"},"products":["Apache Qpid Proton C"],"published":"2026-10-29","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["Apache Software Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105031/"}