{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-64855","id":"CVE-2026-64855","title":"soapbar signature verification bypass in SOAP envelope validation","description":"soapbar is a SOAP library for Python — client, server, and WSDL handling. Prior to version 0.13.0, verify_envelope_bsp() derived its trust anchor from the message it was verifying. It read the X.509 certificate out of the caller-untrusted wsse:BinarySecurityToken, validated only that certificate's not-before / not-after dates, and then verified the signature against that same certificate. There wa","descriptionLong":"soapbar is a SOAP library for Python — client, server, and WSDL handling. Prior to version 0.13.0, verify_envelope_bsp() derived its trust anchor from the message it was verifying. It read the X.509 certificate out of the caller-untrusted wsse:BinarySecurityToken, validated only that certificate's not-before / not-after dates, and then verified the signature against that same certificate. There was no CA-chain validation, no issuer/subject allowlist, and no pinning. A successful verify_envelope_bsp() therefore proved only that the envelope was signed by whoever supplied the embedded certificate — never that it was signed by a trusted party. An attacker who mints their own certificate, signs a forged envelope, and embeds that certificate in the token passes verification. Any consumer that treats a successful BSP verification as authentication can be impersonated (signature forgery / authentication bypass). verify_envelope() (which pins a caller-supplied x509_cert) was not affected — the flaw was specific to the BSP variant whose trust anchor came from the message. This issue has been patched in version 0.13.0.","published":"2026-11-11T15:48:16.347Z","updated":"2026-11-18T21:02:09.155412400Z","reserved":"2026-07-20T18:31:39.291Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"GitHub_M"},"metrics":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"GitHub_M"},{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"github.com"},{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N","rating":"high","source":"OSV"}],"rating":"high","products":["hitoshyamamoto soapbar"],"affectedProducts":[{"vendor":"hitoshyamamoto","product":"soapbar","defaultStatus":null,"versions":[{"version":"< 0.13.0","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-295","CWE-347"],"aliases":["GHSA-859w-52fx-hcm6"],"references":[{"url":"https://github.com/hitoshyamamoto/soapbar/security/advisories/GHSA-859w-52fx-hcm6","tags":["x_refsource_CONFIRM","advisory"]},{"url":"https://github.com/hitoshyamamoto/soapbar/pull/71","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/hitoshyamamoto/soapbar/releases/tag/v0.13.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64855.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64855","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial"},"epss":0.00191,"epssPercentile":0.08826,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-64855","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64855","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-64855","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-64855","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}