signxml
Affected
- introduced
0, fixed4.0.4(ecosystem)
Fixed versions
4.0.4
Fix
- Fixed version
4.0.4pip install --upgrade signxml==4.0.4
Advisory
Also known as: CVE-2025-48994, PYSEC-2026-1921
SignXML's signature verification with HMAC is vulnerable to an algorithm confusion attack
When verifying signatures with X509 certificate validation turned off and HMAC shared secret set (signxml.XMLVerifier.verify(require_x509=False, hmac_key=...), prior versions of SignXML are vulnerable to a potential algorithm confusion attack. Unless the user explicitly limits the expected signature algorithms using the signxml.XMLVerifier.verify(expect_config=...) setting, an attacker may supply a signature unexpectedly signed with a key other than the provided HMAC key, using a different (asymmetric key) signature algorithm.
Starting with signxml 4.0.4, specifying hmac_key causes the set of accepted signature algorithms to be restricted to HMAC only, if not already restricted by the user.
Medium Basis: The source's own band: MODERATE
0, fixed 4.0.4 (ecosystem)4.0.4
4.0.4pip install --upgrade signxml==4.0.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0