Read the docs

soapbar: verify_envelope_bsp accepts unauthenticated embedded certificate

Priority MEDIUM 41CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Spoofing, Security bypass
Confidentiality · integrity · availability
Low · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-295 and CWE-347.

Summary

soapbar, a SOAP library for Python by hitoshyamamoto, is affected before 0.13.0 (CWE-295, CWE-347). verify_envelope_bsp() takes its trust anchor from the wsse:BinarySecurityToken certificate embedded in the message, which the caller does not trust, and checks only that certificate's validity dates before verifying the signature against it. A remote attacker can mint their own certificate, sign a forged envelope and embed that certificate to pass verification without authentication. Any application that treats a successful BSP verification as authentication can be impersonated, while verify_envelope(), which pins a caller-supplied certificate, is not affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00191 8th percentileScored 2026-11-16
Fix Fixed soapbar (hitoshyamamoto): 0.13.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
hitoshyamamotosoapbarbefore 0.13.00.13.0Patch availableCNA
  • soapbar Vendorhitoshyamamoto Affected before 0.13.0 Fixed in 0.13.0 Patch available CNA

Remediation

Upgrade soapbar to version 0.13.0, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

  • Fix · CNA soapbar (hitoshyamamoto) Fixed in 0.13.0

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-64855
  2. 2026-11-12 CISA SSVC decision points changed

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences