CVE-2026-64855 Details
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 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.
A vulnerability exists in the soapbar library for Python, specifically in versions prior to 0.13.0, within the 'verify_envelope_bsp()' function. This function improperly derived its trust anchor from the message being verified, relying on the X.509 certificate embedded in the caller-untrusted 'wsse:BinarySecurityToken'. It only validated the certificate's not-before and not-after dates, allowing an attacker to embed a forged certificate, sign a fake envelope, and pass verification. This flaw could lead to signature forgery and authentication bypass, especially for consumers treating successful BSP verification as authentication. The issue has been patched in version 0.13.0.
Users can upgrade to soapbar version 0.13.0, which requires a trust anchor for 'verify_envelope_bsp()' verification. If BSP verification is necessary, validate the embedded certificate against a trusted store before relying on the verification result.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 11, 2026CISA-ADP
Assessed Nov 12, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/hitoshyamamoto/soapbar/pull/71 | [email protected] | Source CodeVendor |
| https://github.com/hitoshyamamoto/soapbar/releases/tag/v0.13.0 | [email protected] | Release NotesVendor |
| https://github.com/hitoshyamamoto/soapbar/security/advisories/GHSA-859w-52fx-hcm6 | [email protected] | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-295 | Improper Certificate Validation | [email protected] |
| CWE-347 | Improper Verification of Cryptographic Signature | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| soapbar | < 0.13.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 12, 2026 | CVE Modified | CISA-ADP |
| Nov 11, 2026 | New CVE Received | [email protected] |
Volerion