rfc3161-client
Affected
- introduced
0, fixed1.0.3(ecosystem)
Fixed versions
1.0.3
Fix
- Fixed version
1.0.3pip install --upgrade rfc3161-client==1.0.3
Advisory
Also known as: CVE-2025-52556, PYSEC-2026-525
rfc3161-client has insufficient verification for timestamp response signatures
Impact
rfc3161-client 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce _any_ TSR signature so long as the embedded leaf chains up to some root TSA.
Patches
Users should immediately upgrade to rfc3161-client 1.0.3 or later.
Workarounds
There is no workaround possible. Users should immediately upgrade to a fixed version.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.0.3 (ecosystem)1.0.3
1.0.3pip install --upgrade rfc3161-client==1.0.3Fix 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